-
1. Re: Wildfly cluster check using JGroups
pferraro Feb 11, 2019 12:36 PM (in response to gminog)You can view the cluster membership from any node via the following management CLI command:
/subsystem=jgroups/channel=ee:read-attribute(name=view)
-
2. Re: Wildfly cluster check using JGroups
gminog Feb 16, 2019 6:15 AM (in response to pferraro)Hello pferraro, thank you for your response!
Could you please elaborate on the exact steps?
-
3. Re: Wildfly cluster check using JGroups
rhusar Feb 19, 2019 9:14 AM (in response to gminog)First boot your cluster, then run the jboss-cli.sh (or bat if on windows) and run the following command as shown here:
[rhusar@ribera wildfly-16.0.0.CR1-SNAPSHOT]$ ./bin/jboss-cli.sh -c [standalone@localhost:9990 /] /subsystem=jgroups/channel=ee:read-attribute(name=view) { "outcome" => "success", "result" => "[node2|1] (2) [node2, node1]" }
This shows the current coordinator, monotonically increasing view ID, number of cluster members, followed by a complete list of cluster members' logical names.
-
4. Re: Wildfly cluster check using JGroups
gminog Feb 19, 2019 10:53 AM (in response to rhusar)Thank you rhusar !
If I check with the default channel (i.e. channel=ee) then I'm getting a successful outcome.
However, there is no "result" property in the JSON response.
Is there anything else I should check before concluding that no nodes are connected to the cluster (or no cluster exists at all)?
-
5. Re: Wildfly cluster check using JGroups
rhusar Feb 21, 2019 8:54 AM (in response to gminog)If you are not getting any result, it means that the channel is not started. You might be using a different channel or have no deployments that require starting clustering services.