[ARTEMIS-2916] Two servers becoming Live using JDBC Shared Store

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Information Provided
• Affects Version/s: 2.13.0
• Component/s: Broker
• Assignee: Francesco Nigro
• Reporter: Apache Dev
• Created: 24/Sep/20 16:59
• Updated: 20/Oct/21 13:05
• Resolved: 20/Oct/21 13:05

Description

We have similar scenario described in ARTEMIS-2421 but using:

• Artemis 2.13.0
• JDBC Shared Store
• 1 Master currently down
• 3 Slave
  • 1 Live
  • 2 Backup

All 3 slaves are configured with:

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

 
After 2 days of activities, with a single slave working as live we got suddenly one slave server becoming live too while the other live server was still working. No warnings/errors available. Just backup server started creating configured addresses, queues and starting connectors, then it logged "AMQ221010: Backup Server is now live". 

The third slave broker started in the meanwhile to log continuously:

AMQ212034: There are more than one servers on the network broadcasting the same node id. You will see this message exactly once (per node) if a node is restarted, in which case it can be safely ignored. But if it is logged continuously it means you really do have more than one node on the same network active concurrently with the same node id. This could occur if you have a backup node active at the same time as its live node. nodeID=...

 

Final scenario was:

• 1 Master down
• 3 Slave
  • 2 Live
  • 1 Backup 

I see that ARTEMIS-2421 was fixed only in the filesystem use-case. Should it be fixed for JDBC too?

 

Issue Links

• is related to: ARTEMIS-2926 Scheduled task executions are skipped randomly