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

Topology Incorrectly Reported in Shared Store Cluster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Undefined Undefined
    • None
    • AMQ 7.10.2.GA, AMQ 7.11.1.GA
    • clustering, high-availability
    • None
    • False
    • None
    • False
    • Hide

      1. Configure a cluster of 2 or more shared-store broker pairs (sample configuration attached)
      2. Start all master and backup brokers
      3. Log into the the web console for one of the live brokers and verify that the expected number of master and backup brokers are present
      4. Stop the backup brokers one by one, leaving the masters up
      5. Monitor the web console. The number of reported masters and backups remains unchanged and the topology attribute on the cluster-connection continues to show all live and backup brokers
      6. Restart one of the master brokers, leaving the backups down.
      7. Now the status page reflects one of the backups as missing
      8. Restart another of the master brokers.
      9. Again the backup count is decremented

      Show
      1. Configure a cluster of 2 or more shared-store broker pairs (sample configuration attached) 2. Start all master and backup brokers 3. Log into the the web console for one of the live brokers and verify that the expected number of master and backup brokers are present 4. Stop the backup brokers one by one, leaving the masters up 5. Monitor the web console. The number of reported masters and backups remains unchanged and the topology attribute on the cluster-connection continues to show all live and backup brokers 6. Restart one of the master brokers, leaving the backups down. 7. Now the status page reflects one of the backups as missing 8. Restart another of the master brokers. 9. Again the backup count is decremented
    • Important

      In a broker cluster comprised of shared store pairs, the topology incorrectly reflects the backups still being connected and live when they are stopped without restarting the corresponding master brokers.

      The topology display in the console remains green and continues to report all lives and backups being up when the backups are down. This could lead to failover issues, as it is unclear that the backup is not running until the corresponding live broker is stopped.

      This behavior has been confirmed in 7.10.2, 7.10.3, and 7.11.1 versions.

        1. broker-s.xml
          12 kB
        2. broker-m.xml
          12 kB

              rhn-support-jbertram Justin Bertram
              rhn-support-dhawkins Duane Hawkins
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: