You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2020/01/10 02:12:00 UTC
[jira] [Resolved] (ARTEMIS-2250) Shared store lock is not monitored
while running
[ https://issues.apache.org/jira/browse/ARTEMIS-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram resolved ARTEMIS-2250.
-------------------------------------
Resolution: Duplicate
> Shared store lock is not monitored while running
> ------------------------------------------------
>
> Key: ARTEMIS-2250
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2250
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.6.4
> Environment: AWS EFS (NFS)
> Reporter: Bas
> Priority: Major
>
> When using the shared store the live server can loose the lock on the journal but does not notice it. This can happen when a shared file system is being used like in AWS where we use EFS.
> This can cause problems when the live server regains the network file system connection and just continues to process messages. At some point the live or the backup quits because it notices changes on the filesystems which it did not do itself.
> We were able to prevent the occurence by tweaking EFS connection settings so it does not occur anymore in our setup.
> For artemis we would like to show our change maybe someone can review the change and see if it can be improved and adapted in artemis.
> Patch is here for master:
> https://github.com/emagiz/activemq-artemis/commit/788adfbd3e5a54c63eed0810b7377641684b6fe1.patch
> Pull request:
> https://github.com/apache/activemq-artemis/pull/2547
--
This message was sent by Atlassian Jira
(v8.3.4#803005)