[
https://issues.apache.org/jira/browse/ARTEMIS-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16164470#comment-16164470
]
ASF subversion and git services commented on ARTEMIS-1417:
----------------------------------------------------------
Commit 2ec173bc708daca163c9356cf12440432abc61c4 in activemq-artemis's branch
refs/heads/master from [~jbertram]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=2ec173b ]
ARTEMIS-1417 Failback not working on NFSv4
With NFSv4 it is now necessary to lock/unlock the byte of the server
lock file where the state information is written so that the
information is then flushed to the other clients looking at the file.
> Failback not working on NFSv4
> -----------------------------
>
> Key: ARTEMIS-1417
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1417
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.3.0
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Fix For: 2.4.0
>
>
> If Artemis is using NFSv4 as shared store for its messaging journal to
> provide HA then a write to server.lock made by one server may not be
> propagated to the other server. This prevents failback from happening. This
> is change in behavior in data synchronization between two NFSv4 clients was
> observed when recently upgrading Linux platforms.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
