[ClusterLabs] corosync totem.token too long may cause pacemaker(cluster) unstable?

[Jan Friesse]

> 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?

What corosync version are you using? Your config file is not exactly 
"broken", but I'm not sure how exactly all the settings play together, 
so maybe minimize it. Setting high token timeout shouldn't cause 
problems, only failure detection takes long time.


>
> 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
>          }
> }
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://lists.clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>