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

[cys]

At 2017-03-08 17:10:36, "Jan Friesse" <jfriesse at redhat.com> wrote:
>> 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.
>
>

Corosync Cluster Engine, version '2.4.0'
Copyright (c) 2006-2009 Red Hat, Inc.

Sometimes corosync took very long time to be in operational state. I'm not sure whether it's related with totem.token.
Could you tell me how to diagnose it?

Thanks.