Thanks, I had been expecting some magic user-level command to be used. C programming is probably efficient, but I#ll have to write another tool first.
It seems the corosync-quorumtool can also provide the information. Is it correct that the "ring id" has the node id of the DC? Like here (node id 116 is the DC): ------------------ Date: Thu Feb 25 11:24:08 2021 Quorum provider: corosync_votequorum Nodes: 3 Node ID: 119 Ring ID: 116/42660 Quorate: Yes Regards, Ulrich >>> Christine Caulfield <[email protected]> schrieb am 25.02.2021 um 08:22 in Nachricht <[email protected]>: > The most efficient way of getting corosync facts about nodes/quorum is > to use the votequorum API. > > see /usr/include/corosync/votequorum.h > and in the corosync sources tarball tests/testvotequorum1.c > > CHrissie > > > On 25/02/2021 07:16, Ulrich Windl wrote: >> Hi! >> >> I'm thinking about some simple cluster status display that is updated > periodically. >> I wonder how to get some "cluster facts" efficiently. Among those are: >> >> * Is corosync running, and how many nodes can be seen? >> * Is Pacemaker running, how many nodes does it see, and does it have a > quorum? >> * Is the current node DC? >> * How many resources matching some regular expression are running? >> >> Regards, >> Ulrich >> >> >> >> _______________________________________________ >> Manage your subscription: >> https://lists.clusterlabs.org/mailman/listinfo/users >> >> ClusterLabs home: https://www.clusterlabs.org/ >> > > _______________________________________________ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
