Re: [ClusterLabs] Corosync unable to reach consensus for membership

2019-05-02 Thread Jan Friesse
Prasad, Hello Jan, Please block both input and output. Corosync isn't able to handle byzantine faults. Thanks. It results in clean partition if I block both outgoing and incoming udp traffic to and from a given node. Good However, could you suggest me what is the best way to handle

Re: [ClusterLabs] Corosync unable to reach consensus for membership

2019-05-01 Thread Prasad Nagaraj
Hello Jan, >Please block both input and output. Corosync isn't able to handle >byzantine faults. Thanks. It results in clean partition if I block both outgoing and incoming udp traffic to and from a given node. However, could you suggest me what is the best way to handle any real world

Re: [ClusterLabs] Corosync unable to reach consensus for membership

2019-04-30 Thread Jan Friesse
Prasad, Hello : I have a 3 node corosync and pacemaker cluster and the nodes are: Online: [ SG-azfw2-189 SG-azfw2-190 SG-azfw2-191 ] Full list of resources: Master/Slave Set: ms_mysql [p_mysql] Masters: [ SG-azfw2-189 ] Slaves: [ SG-azfw2-190 SG-azfw2-191 ] For my network

[ClusterLabs] Corosync unable to reach consensus for membership

2019-04-30 Thread Prasad Nagaraj
Hello : I have a 3 node corosync and pacemaker cluster and the nodes are: Online: [ SG-azfw2-189 SG-azfw2-190 SG-azfw2-191 ] Full list of resources: Master/Slave Set: ms_mysql [p_mysql] Masters: [ SG-azfw2-189 ] Slaves: [ SG-azfw2-190 SG-azfw2-191 ] For my network partition test, I