You can bump the 'token' to a higher value (for example 10s ) and adjust the
consensus based on that value. See man 5 corosync.conf
Don't forget to sync the nodes and reload the corosync stack.
Of course proper testing on non-Prod is highly recommend.
Note: Both parameters use milliseconds (at
Hi,
I manage an active/passive PostgreSQL cluster using DRBD, LVM, Pacemaker and
Corosync on a Debian GNU/Linux operating system.
Everything is OK, but my platform seems to be quite "sensitive" to small
network timeouts which are generating a cluster migration start from active to
passive
