You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Karan Aggarwal (Jira)" <ji...@apache.org> on 2021/02/04 07:17:00 UTC

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

    [ https://issues.apache.org/jira/browse/ARTEMIS-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17278607#comment-17278607 ] 

Karan Aggarwal commented on ARTEMIS-2808:
-----------------------------------------

Hi [~jbertram],

Yes, I would be able to test the potential fix on this.

To simulate, we used 2 machines with Windows OS on the same network.

We shared a directory from one of the windows machine. This directory was used as shared store location in broker.xml

 

Please let me know if you need more information on simulating the use-case.

Also, do let me know an estimated time when we can get the potential fix?

 

 

> 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
>         Attachments: Scenario_1.zip, Scenario_2.zip
>
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)