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

If a slave is isolated it should stay passive

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • AMQ 7.0.1.GA
    • A-MQ 7.0.0.ER12, A-MQ 7.0.0.CR1
    • None
    • AMQ Sprint 1

      When isolating a slave (backup) network from the other nodes in the topology, slave becomes live after a while. We are using IPTABLES command in the test scenario.

      test1:
      iptables -A INPUT -p tcp --dport 61616 -j DROP
      iptables -A OUTPUT -p tcp --dport 61616 -j DROP
      iptables -A OUTPUT -p udp --dport 9876 -j DROP
      iptables -A INPUT -p udp --dport 9876 -j DROP

      test2:
      iptables -A INPUT -p tcp --dport 61616 -j REJECT
      iptables -A OUTPUT -p tcp --dport 61616 -j REJECT
      iptables -A OUTPUT -p udp --dport 9876 -j REJECT
      iptables -A INPUT -p udp --dport 9876 -j REJECT

      If a slave is isolated it should stay passive to avoid split brains.

        1. artemis.master02.log
          176 kB
        2. artemis.slave02.log
          168 kB
        3. artemis.master01.log
          196 kB
        4. artemis.slave01.log
          1.03 MB
        5. artemis.master01.log
          7 kB
        6. artemis.master03.log
          12 kB
        7. artemis.slave01.log
          7 kB
        8. artemis.slave02.log
          7 kB
        9. artemis.slave03.log
          5 kB
        10. artemis.master02.log
          16 kB
        11. broker_config.zip
          68 kB
        12. splitbrain.tgz
          65 kB
        13. s1-artemis.log
          2.42 MB

              rh-ee-ataylor Andy Taylor
              rhn-gps-bmachado Bruno Rossetto Machado (Inactive)
              Michal Toth Michal Toth
              Votes:
              1 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: