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

[HA, MS1S2] Failback from slave1 back to master is not working

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Critical Critical
    • None
    • AMQ 7.1.0.GA, AMQ 7.1.1.GA
    • clustering, high-availability
    • None
    • Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration, User Experience
    • Hide
      1. kill master
      2. slave1 should take over - OK
      3. slave2 becomes backup for slave1 - OK
      4. When master is started again, master should become active, slave1 should go as backup - NOK

      Outcome: master becomes lone slave (no HA pair), despite the fact, failback should happen.
      When live slave1 is killed, master becomes live again as expected. - OK

      Show
      kill master slave1 should take over - OK slave2 becomes backup for slave1 - OK When master is started again, master should become active, slave1 should go as backup - NOK Outcome: master becomes lone slave (no HA pair), despite the fact, failback should happen. When live slave1 is killed, master becomes live again as expected. - OK

      Similar to what ENTMQBR-1021 describes, but when master is killed and slave1 takes over (acting as live), ressurected master does not failback (slave1 holds liveness token).

      This is present in artemis 2.5.0

      Master
<broadcast-groups>
      <broadcast-group name="my-broadcast-group">
        <group-address>231.7.7.7</group-address>
        <group-port>9876</group-port>
        <broadcast-period>5000</broadcast-period>
        <connector-ref>artemis</connector-ref>
      </broadcast-group>
    </broadcast-groups>
    <discovery-groups>
      <discovery-group name="my-discovery-group">
        <group-address>231.7.7.7</group-address>
        <group-port>9876</group-port>
        <refresh-timeout>5000</refresh-timeout>
      </discovery-group>
    </discovery-groups>
    <cluster-connections>
      <cluster-connection name="my-cluster">
        <connector-ref>artemis</connector-ref>
        <message-load-balancing>ON_DEMAND</message-load-balancing>
        <max-hops>1</max-hops>
        <discovery-group-ref discovery-group-name="my-discovery-group"/>
      </cluster-connection>
    </cluster-connections>
    <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>

slave1 and 2 (identical)
<broadcast-groups>
      <broadcast-group name="my-broadcast-group">
        <group-address>231.7.7.7</group-address>
        <group-port>9876</group-port>
        <broadcast-period>5000</broadcast-period>
        <connector-ref>artemis</connector-ref>
      </broadcast-group>
    </broadcast-groups>
    <discovery-groups>
      <discovery-group name="my-discovery-group">
        <group-address>231.7.7.7</group-address>
        <group-port>9876</group-port>
        <refresh-timeout>5000</refresh-timeout>
      </discovery-group>
    </discovery-groups>
    <cluster-connections>
      <cluster-connection name="my-cluster">
        <connector-ref>artemis</connector-ref>
        <message-load-balancing>ON_DEMAND</message-load-balancing>
        <max-hops>1</max-hops>
        <discovery-group-ref discovery-group-name="my-discovery-group"/>
      </cluster-connection>
    </cluster-connections>
    <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>

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

                Created:
                Updated:
                Resolved: