[
https://issues.apache.org/jira/browse/ARTEMIS-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17142194#comment-17142194
]
Francesco Nigro edited comment on ARTEMIS-2808 at 6/22/20, 4:03 PM:
--------------------------------------------------------------------
If you're using a remote storage, ideally you should handle the I/O failure at
the remote disk configuration level: is like removing the disk of the broker
while it's running...which guarantees you will get from it?
Anway, please share some logs (possibly DEBUG) to help diagnose what's going
on: the expectation is that the current master would crash and the backup
should reattempt over and over again (until lockAcquisitionTimeout) to acquire
the lock when the remote storage is disconnected.
was (Author: [email protected]):
If you're using a remote storage, ideally you should handle the I/O failure at
the remote disk configuration level: is like removing the disk of the broker
while it's running...which guarantees you will get from it?
> Artemis HA with shared storage strategy does not reconnect with shared
> storage if reconnection happens at shared storage
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-2808
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2808
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.11.0
> Environment: Windows 10
> Reporter: Karan Aggarwal
> Priority: Blocker
>
> We verified the behavior of Artemis HA by bringing down the Shared Location
> (VM) while run is in progress and here is the observation:
> *Scenario:*
> * When Artemis services are up and running and run is in progress, Restarted
> the Shared Location Machine
> * Shared location was up in 5 mins
> * Both Artemis Master and Slave did not connect back to the Shared Location
> * Tried stopping the Artemis Services - Slave service stopped. But Master
> service did not stop. We had to kill the Process.
> * Tried to start the Artemis Services: Master service did not start up at
> all.
> * Slave service started successfully.
> * 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
