Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-15039

Cluster Intermittently Fails to Reestablish After a Node is Restarted

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 25.0.0.Beta1, 25.0.0.Final
    • 18.0.1.Final, 23.0.2.Final, 24.0.0.Final
    • Clustering, JMS
    • None
    • Hide

      Set up a two-node messaging cluster with configuration similar to that attached. Start up both cluster machines and wait for the cluster to establish and report a non-empty cluster node list:

      [standalone@node1.test.redhat.com:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster:get-nodes()
{
    "outcome" => "success",
    "result" => {"f982abf8-26d2-11eb-8964-5254009ef848" => "192.168.100.102/192.168.100.102:8080"}
}

      Restart each node one at a time, with varying intervals between stopping and restarting the node. After each restart, check the node list in the cli. It may take a number of tries to reproduce the issue. Once the node list is empty, it remains empty, even after waiting for some time.

      Show
      Set up a two-node messaging cluster with configuration similar to that attached. Start up both cluster machines and wait for the cluster to establish and report a non-empty cluster node list: [standalone@node1.test.redhat.com:9990 /] /subsystem=messaging-activemq/server= default /cluster-connection=my-cluster:get-nodes() { "outcome" => "success" , "result" => { "f982abf8-26d2-11eb-8964-5254009ef848" => "192.168.100.102/192.168.100.102:8080" } } Restart each node one at a time, with varying intervals between stopping and restarting the node. After each restart, check the node list in the cli. It may take a number of tries to reproduce the issue. Once the node list is empty, it remains empty, even after waiting for some time.
    • Undefined

      In a simple (non-HA) load-balancing cluster, sometimes restarting one node of the cluster results in the cluster failing to get reestablished, with the result that the cluster topology is reported as empty in the cli:

      [standalone@node1.test.redhat.com:9990 /] /subsystem=messaging-activemq/server=default/cluster-connection=my-cluster:get-nodes()
{
    "outcome" => "success",
    "result" => {}
}

      The cluster in question is using jgroups-UDP.

              pferraro@redhat.com Paul Ferraro
              pferraro@redhat.com Paul Ferraro
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: