Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-2307

after fabric ensemble quorum recovered; no master elected in A-MQ master/slave cluster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • jboss-fuse-6.2
    • jboss-fuse-6.0
    • ActiveMQ
    • None
    • % %
    • Hide

      create a fabric with 3 ensemble containers

      - fabic-create
- container-add-profile root fmc
- container-create-child root en1
- container-create-child root en2
- ensemble-add en1 en2

      Create a master/slave setup

      - fabric:container-create-child root AMQ-East 2
- fabric:mq-create --group amq-east  --assign-container AMQ-East1,AMQ-East2 amq-east-profile
      • cluster-list
        [cluster] [masters] [slaves] [services]
        fusemq/amq-east
        amq-east-profile AMQ-East1 AMQ-East2 tcp://sideshow.home:65518

      upgrade fabric to patch 6.0R2P2

      loose the quorum of ensemble containers:
      in a regular terminal kill en1 container's java process
      in a regular terminal kill en2 container's java process

      leave for 2 minutes to allow fabric to detect failures etc.

      restart ensemble containers

      - boss-fuse-6.0.0.redhat-024/instances/en1/bin/start
- boss-fuse-6.0.0.redhat-024/instances/en2/bin/start

      a cluter list shows:

      [cluster]                      [masters]                      [slaves]                       [services]
fusemq/amq-east
   amq-east-profile            AMQ-East2                      AMQ-East1, AMQ-East2, AMQ-East1 tcp://sideshow.home:49179

      Result:

      • broker is not be reached on tcp://sideshow.home:49179, from the logs broker was shutdown in the log files for AMQ-East2
      Show
      create a fabric with 3 ensemble containers - fabic-create - container-add-profile root fmc - container-create-child root en1 - container-create-child root en2 - ensemble-add en1 en2 Create a master/slave setup - fabric:container-create-child root AMQ-East 2 - fabric:mq-create --group amq-east --assign-container AMQ-East1,AMQ-East2 amq-east-profile cluster-list [cluster] [masters] [slaves] [services] fusemq/amq-east amq-east-profile AMQ-East1 AMQ-East2 tcp://sideshow.home:65518 upgrade fabric to patch 6.0R2P2 loose the quorum of ensemble containers: in a regular terminal kill en1 container's java process in a regular terminal kill en2 container's java process leave for 2 minutes to allow fabric to detect failures etc. restart ensemble containers - boss-fuse-6.0.0.redhat-024/instances/en1/bin/start - boss-fuse-6.0.0.redhat-024/instances/en2/bin/start a cluter list shows: [cluster] [masters] [slaves] [services] fusemq/amq-east amq-east-profile AMQ-East2 AMQ-East1, AMQ-East2, AMQ-East1 tcp: //sideshow.home:49179 Result: broker is not be reached on tcp://sideshow.home:49179, from the logs broker was shutdown in the log files for AMQ-East2

      After the ensemble quorum is lost and recovered; no broker is elected in a master/slave cluster.

      Workaround: restart all the broker containers.

        1. AMQ_EAST1-RESTART-karaf.log
          720 kB
        2. AMQ_EAST2-RESTART-karaf.log
          463 kB
        3. fabric-groups-7.2.0.redhat-024.jar
          60 kB
        4. entmq837.diff
          8 kB
        5. entesb-2307.png
          entesb-2307.png
          46 kB

              ggrzybek Grzegorz Grzybek
              rhn-support-pfox Patrick Fox (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: