在2017年03月13 09时35分, "bliu"<[email protected]>写道: Hi, There is waitforall on nodeC, while not on nodeB, could you disable waitforall no nodeC And then have a re-try. On 03/11/2017 10:50 AM, cys wrote: We have a cluster containing 3 nodes(nodeA, nodeB, nodeC). After nodeA is taken offline(by ifdown, this may be not right?), nodeC cannot acquire quorum while nodeB can. NodeC: corosync-quorumtool -s Quorum information ------------------ Date: Sat Mar 11 10:42:22 2017 Quorum provider: corosync_votequorum Nodes 2 Node ID: 2 Ring ID: 2/24 Quorate: No Votequorum information ---------------------- Expected votes: 3 Highest expected: 3 Total votes: 2 Quorum: 2 Activity blocked Flags: WaitForAll Membership information ---------------------- Nodeid Votes Name 2 1 68.68.68.15 (local) 3 1 68.68.68.16 NodeB: corosync-quorumtools -s Quorum information ------------------ Date: Sat Mar 11 10:45:44 2017 Quorum provider: corosync_votequorum Nodes: 2 Node ID: 3 Ring ID: 2/24 Quorate: Yes Votequorum information ---------------------- Expected votes: 3 Highest expected: 3 Total votes: 2 Quorum: 2 Flags: Quorate Membership information ---------------------- Nodeid Votes Name 2 1 68.68.68.15 3 1 68.68.68.16 (local) So what's the problem? Thanks. _______________________________________________ Users mailing list: [email protected]http://lists.clusterlabs.org/mailman/listinfo/usersProject Home: http://www.clusterlabs.orgGetting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdfBugs: http://bugs.clusterlabs.org
_______________________________________________ Users mailing list: [email protected] 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
