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

ASF GitHub Bot commented on ARTEMIS-1417:
-----------------------------------------

GitHub user jbertram opened a pull request:

    https://github.com/apache/activemq-artemis/pull/1530

    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.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-1417

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/1530.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1530
    
----
commit d52828ed6a59f16f94e5ef1445b4b7b28802b81b
Author: Justin Bertram <jbert...@apache.org>
Date:   2017-09-12T16:17:08Z

    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)

Reply via email to