[ClusterLabs] corosync totem.token too long may cause pacemaker(cluster) unstable?
cys
chaoys155 at 163.com
Wed Mar 8 02:28:03 EST 2017
Hi,
We changed totem.token from 3s to 60s. Then something strange were observed, such as unexpected node offline.
I read corosync.conf manpage, but still don't understand the reason.
Can anyone explain this? or maybe our conf is broken?
Our corosync.conf:
compatibility: whitetank
quorum {
provider: corosync_votequorum
two_node: 0
}
totem {
version: 2
token: 60000
token_retransmits_before_loss_const: 10
join: 60
consensus: 3600
vsftype: none
max_messages: 20
clear_node_high_bit: yes
rrp_mode: none
secauth: off
threads: 2
transport: udpu
interface {
ringnumber: 0
bindnetaddr: 39.39.0.5
mcastport: 5405
}
}
amf {
mode: disabled
}
aisexec {
user: root
group: root
}
nodelist {
node {
ring0_addr: 39.39.0.4
nodeid: 1
}
node {
ring0_addr: 39.39.0.5
nodeid: 2
}
node {
ring0_addr: 39.39.0.6
nodeid: 3
}
}
More information about the Users
mailing list