Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-4438

[GSS](7.3.z) Cluster Intermittently Fails to Reestablish After a Node is Restarted

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Critical
    • None
    • None
    • broker-core, clustering
    • None
    • False
    • False
    • Undefined
    • 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.

    Description

      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.

      Attachments

        1. 01-07-legacy.tar.gz
          176 kB
        2. artemis-server-2.9.0.jar
          1.81 MB
        3. debug-jboss-broadcast-endpoint.tar.gz
          2.79 MB
        4. jboss-debug-wildfly-endpoint.tar.gz
          1.13 MB
        5. logs.zip
          512 kB
        6. logs-01-07.tar.gz
          690 kB
        7. logs-7.3.6.zip
          479 kB
        8. logs-7.3.6-1.zip
          479 kB
        9. quicklab.tar.gz
          435 kB

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-20522 [GSS](7.3.z) WFLY-15039 - Cluster Intermittently Fails to Reestablish After a Node is Restarted

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              dbruscin Domenico Francesco Bruscino
              rhn-support-dhawkins Duane Hawkins
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: