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

Resurrected (becames live) master broker is not sharing data properly, identifies as "undefined" and prohibits it's slave to join cluster (HA topology)

XMLWordPrintable

    • Hide

      Env: 3 pairs (master-slave)

      1. Kill master1, slave1 becomes live (allow-failback on slave true)
      2. Start master1 again.
      3. Slave1 gives control to master1
      4. Master1 identifies as "undefined" with unknown IP etc
      Show
      Env: 3 pairs (master-slave) Kill master1, slave1 becomes live (allow-failback on slave true) Start master1 again. Slave1 gives control to master1 Master1 identifies as "undefined" with unknown IP etc

      When master slave which was killed becomes active again (resurrected) and joins cluster in HA topology, it does not share its nodeId, IP address etc. It just reports itself as "undefined".

      Other (live) brokers can see it, but can't figure out its details.

      Also if this broker took control from it's ex-live slave (allow-failback), this slave disappears from topology. Restarting of slave does not help. We have to stop this slave and master, and start master and slave again.

      See related jira ENTMQBR-932 for details.

              rh-ee-ataylor Andy Taylor
              mtoth@redhat.com Michal Toth
              Michal Toth Michal Toth
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: