There are two ways of finding the Group Leader node of a specific group:
/usr/sbin/rsct/bin/hagsns -s hags
The output is similar to:
HA GS NameServer Status NodeId=6.14, pid=10094, domainId=6.14, NS established, CodeLevel=GSlevel(DRL=8) NS state=kBecomeNS, protocolInProgress=kNoProtocol, outstandingBroadcast=kNoBcast Process started on Jun 19 18:35:55, (10d 20:22:39) ago. HB connection took (0:0:0). Initial NS certainty on Jun 19 18:36:12, (10d 20:22:22) ago, taking (0:0:16). Our current epoch of certainty started on Jun 23 13:05:18, (7d 1:53:16) ago. Number of UP nodes: 12 List of UP nodes: 0 1 5 6 7 8 9 11 17 19 23 26 List of known groups: 1.1 cssMembership: GL: 6 seqNum: 73 theIPS: 6 1 26 17 0 8 7 9 5 11 lookupQ: 2.1 ha_em_peers: GL: 6 seqNum: 30 theIPS: 6 0 8 7 5 11 lookupQ:
The bottom few lines display the group membership information. For example, the GL node of the group cssMembership is node 6, and its participating nodes are "6 1 26 17 0 8 7 9 5 11".
hagsvote -s hags
The output is similar to:
Number of groups: 3 Group slot #[0] Group name [HostMembership] GL node [Unknown] voting data: No protocol is currently executing in the group. -------------------------------------------------- Group slot #[1] Group name [cssRawMembership] GL node [Unknown] voting data: No protocol is currently executing in the group. -------------------------------------------------- Group slot #[2] Group name [cssMembership] GL node [6] voting data: No protocol is currently executing in the group.
In this output, node 6 is the GL node of the group cssMembership. If the GL node is Unknown, this indicates that no client applications tried to use the group on this node.