[
https://issues.apache.org/jira/browse/ARTEMIS-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16989171#comment-16989171
]
ASF subversion and git services commented on ARTEMIS-2567:
----------------------------------------------------------
Commit 04db90eddeda6df406c984da95e95a2b425c6c54 in activemq-artemis's branch
refs/heads/master from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=04db90e ]
ARTEMIS-2567 restore locking semantics on server.lock when reading status
> Shared-store failback broken on NFS
> -----------------------------------
>
> Key: ARTEMIS-2567
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2567
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.10.1
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Fix For: 2.11.0
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> The changes from ARTEMIS-2441 caused a regression of the issue fixed by
> ARTEMIS-1417.
> The changes in ARTEMIS-1417 made sure to lock/unlock the {{server.lock}} file
> when reading the state information in order to deal with stale data over NFS.
> However, the changes from ARTEMIS-2441 split the lock into several different
> files which means that when the state information is read now the
> {{server.lock}} file itself is not locked/unlocked which results in reading
> stale data on the slave.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
