0
votes

I have Artemis configuration (shared storage) with following ha-policy (for master and slave):

Master:

<ha-policy>
  <shared-store>
    <master>
      <failover-on-shutdown>true</failover-on-shutdown>
    </master>
  </shared-store>
</ha-policy>

Slave:

<ha-policy>
  <shared-store>
    <slave>
      <failover-on-shutdown>true</failover-on-shutdown>
      <allow-failback>true</allow-failback>
    </slave>
  </shared-store>
</ha-policy>

i am doing the following steps:

  1. Stop Master

./artemis-service stop

Backup is now live:

2020-09-22 10:51:57,172 INFO  [org.apache.activemq.artemis.core.server] AMQ221010: Backup Server is now live
  1. Start Master

./artemis-service start

Master don't switch to live:

2020-09-22 10:53:01,128 INFO  [org.apache.activemq.artemis.core.server] AMQ221034: Waiting indefinitely to obtain live lock
2020-09-22 10:53:01,489 INFO  [org.apache.activemq.artemis.core.server] AMQ221031: backup announced

Is this the correct behavior? Why doesn't the master server become live after restart?

But If I stop the backup server, the master becomes live.

Server version 2.11

I tried to reproduce this on 2.15. Artemis 2.15 works correctly.

1
Have you tried this on the latest release? - Justin Bertram
Thank you! I will try now, but we'll be using the old version for a while. Is this a version 2.11 bug? - Wi-Al
I'm not aware of any specific fix that would necessarily resolve your problem, but it's always a good idea to test on the latest release simply to rule out the possibility that the issue has already been fixed. It would be a big waste of time to do all the work to reproduce and investigate the problem only to find later that it had already been resolved. Version 2.11.0 is pretty old at this point. Hundreds of issues have been resolved in later releases. - Justin Bertram
Ok! I am trying to reproduce the problem in 2.15. Am I correct in my understanding that the config looks correct? - Wi-Al
Everything works correctly at 2.15 - Wi-Al

1 Answers

1
votes

Your configuration looks good.

Please move to the latest release. I believe there were some issues with file locking that have been resolved since 2.11.0.

You can find upgrade instructions in the documentation.