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

[HA-replication 1 pair] - no failback allowed, when master is killed and started again master does not connect to slave HA pair, but creates one himself

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Blocker Blocker
    • None
    • AMQ 7.1.0.GA, AMQ 7.1.1.GA
    • high-availability
    • None
    • Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration, User Experience

      Deployment:
      1 HA pair with configuration provided

          <ha-policy>
      <replication>
        <master>
          <group-name>fish</group-name>
          <vote-on-replication-failure>true</vote-on-replication-failure>
<!--          <check-for-live-server>true</check-for-live-server> -->
        </master>
      </replication>
    </ha-policy>
Slave:
    <ha-policy>
      <replication>
        <slave>
          <group-name>fish</group-name>
          <vote-on-replication-failure>true</vote-on-replication-failure>
         <!-- <allow-failback>true</allow-failback> -->
        </slave>
      </replication>
    </ha-policy>

      Scenario:

      1. Make sure HA pair is formed well - OK
      2. Kill master broker - slave takes control and is live - OK
      3. Start master broker again - master should join as backup - NOK
        instead, master becomes live and disconnects from slave (cluster) - creating his own, resulting in two separate LIVE nodes (slave and master)

      Sidenote:
      If allow-failback is set to true on both slave & master, it's working correctly - master takes control from slave and slave goes to backup. (But bringing down hawtio console)

        1. ha_fail_master_slave.log
          54 kB

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

                Created:
                Updated:
                Resolved: