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

Attribute group-name ignored in replicated colocated configurations

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Done
    • AMQ 7.2.0.GA, AMQ 7.2.1.GA, AMQ 7.2.2.GA, AMQ 7.3.0.GA, AMQ 7.2.3.GA, AMQ 7.2.4.GA
    • AMQ 7.4.2.GA
    • high-availability
    • None
    • AMQ Sprint 3519
    • Hide

      Reproducer configuration attached

      Show
      Reproducer configuration attached
    • Release Notes
    • Hide

      Configure masters / slaves in multiple JVMs

      Show
      Configure masters / slaves in multiple JVMs
    • Hide
      Previously, if you configured a cluster of three master-slave broker pairs to use high availability with colocated backups, the value of the `group-name` attribute of each broker was ignored. As a result, when you started brokers in a new cluster configured this way, the first two master-slave pairs that started immediately began replicating to each other. However, the final master-slave pair that started did not get a replication partner. The final master-slave pair then polled the cluster indefinitely, looking for a partner. This issue is now resolved.
      Show
      Previously, if you configured a cluster of three master-slave broker pairs to use high availability with colocated backups, the value of the `group-name` attribute of each broker was ignored. As a result, when you started brokers in a new cluster configured this way, the first two master-slave pairs that started immediately began replicating to each other. However, the final master-slave pair that started did not get a replication partner. The final master-slave pair then polled the cluster indefinitely, looking for a partner. This issue is now resolved.
    • Documented as Resolved Issue
    • +
    • Verified in a release

    Description

      When configuring colocated master/slave high-availability in a 3-node cluster, group-name settings on master / slave configurations are ignored. As a result, when starting the brokers in the new cluster up, the first 2 nodes in the cluster begin replicating each other and the last node to start up does not get a replication partner and polls indefinitely for a backup.

      Attachments

        Issue Links

          Activity

            People

              fnigro Francesco Nigro (Inactive)
              dbruscin Domenico Francesco Bruscino
              Mikhail Krutov Mikhail Krutov
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: