[ARTEMIS-2808] Artemis HA with shared storage strategy does not reconnect with shared storage if reconnection happens at shared storage

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Cannot Reproduce
• Affects Version/s: 2.11.0

Environment

Windows 10

• Assignee: Unassigned
• Reporter: Karan Aggarwal
• Created: 17/Jun/20 07:35
• Updated: 11/Oct/21 18:58
• Resolved: 11/Oct/21 18:58

Description

We verified the behavior of Artemis HA by bringing down the shared storage (VM) while run is in progress and here is the observation: 

Scenario:

• When Artemis services are up and running and run is in progress we restarted the machine hosting the shared storage
• Shared storage was back up in 5 mins
• Both Artemis master and slave did not connect back to the shared storage
• We tried stopping the Artemis brokers. The slave stopped, but the master did not stop. We had to kill the process.
• We tried to start the Artemis brokers. The master did not start up at all. The slave started successfully.
• We restarted the master Artemis server. Server started successfully and acquired back up.

Shared Storage type: NFS

Impact: The run is stopped and Artemis servers needs to be started again every time shared storage connection goes down momentarily.

Issue Links

• relates to: ARTEMIS-3030 Journal lock evaluation fails when NFS is temporarily disconnected
• relates to: ARTEMIS-2069 Backup doesn't activate after shared store is reconnected