How to calculate corosync main process schedule threshold

Issue

• The 'totem.token' value of 1650 doesn't seem to related to the threshold number in the diagnostic message the corosync service logged: threshold is 1320.0000 ms:

[MAIN  ] Corosync main process was not scheduled for 2145.7053 ms (threshold is 1320.0000 ms). Consider token timeout increase.

• When the totem.token is default 1000 ms, cluster node fence and this was recorded:

[MAIN  ] Corosync main process was not scheduled for 30775.2207 ms (threshold is 800.0000 ms). Consider token timeout increase.

• A node fence operation was triggered as the corosync process was not scheduled with in 4000.0000 ms, consequently the cluster communication token was not replied: in case of token: 5000 on corosync.conf

[MAIN  ] Corosync main process was not scheduled for 11445.4121ms (threshold is 4000.0000 ms). Consider token timeout increase.