Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-12126

Replicated HA: Live doesn't failback if its journal is removed before start

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Critical Critical
    • None
    • 7.1.0.ER2, 7.2.0.GA
    • ActiveMQ
    • None
    • Hide

      Note: Because of JBEAP-11799, the reproducer doesn't work with 7.1.0.ER2. Use 7.1.0.ER1 instead.

      git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
cd eap-tests-hornetq/scripts/
git checkout 01ee60b197d960247c7953cdfe6fceac5e2217b9
groovy -DEAP_VERSION=7.1.0.ER1 PrepareServers7.groovy
export WORKSPACE=$PWD
export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap
export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap
export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap
export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap

cd ../jboss-hornetq-testsuite/

mvn clean test -Dtest=ReplicatedDedicatedFailoverTestCase#testFailbackWithRemovingJournal -DfailIfNoTests=false -Deap=7x | tee log
      Show
      Note: Because of JBEAP-11799 , the reproducer doesn't work with 7.1.0.ER2. Use 7.1.0.ER1 instead. git clone git: //git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ git checkout 01ee60b197d960247c7953cdfe6fceac5e2217b9 groovy -DEAP_VERSION=7.1.0.ER1 PrepareServers7.groovy export WORKSPACE=$PWD export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap cd ../jboss-hornetq-testsuite/ mvn clean test -Dtest=ReplicatedDedicatedFailoverTestCase#testFailbackWithRemovingJournal -DfailIfNoTests= false -Deap=7x | tee log

      Scenario

      1. Start two servers in replicated HA
      2. Wait until they are fully synchronized
      3. Kill live
      4. Delete live's journal
      5. Start live

      Expectation: Live discovers its backup, contact it and does failback.

      Reality: Live doesn't recognize its backup and activates itself. Backup stays active as well.

      Customer impact: This design issue may cause problems in cloud environment where in case of failure, new docker container is started without its previous state.

              rhn-support-jbertram Justin Bertram
              eduda_jira Erich Duda (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: