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 2017/04/17 19:10:41 UTC

[jira] [Resolved] (ARTEMIS-1108) Shared-store with AIO fails to lock lockfile on NFS shares

     [ https://issues.apache.org/jira/browse/ARTEMIS-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram resolved ARTEMIS-1108.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.next

> Shared-store with AIO fails to lock lockfile on NFS shares
> ----------------------------------------------------------
>
>                 Key: ARTEMIS-1108
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1108
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 1.5.4, 2.0.0
>         Environment: Linux with NFS-mounted shared-store directory
>            Reporter: Bernd Gutjahr
>            Priority: Minor
>             Fix For: 2.next
>
>
> When we setup shared-store backup servers with the shared store path pointed to an NFS-mounted directory, file locking didn't work until we disabled AIO and used NIO instead. Although NFS is not recommended and we don't want to use in production, we wanted to use NFS in some test or demo setups just for simplicity.
> As it turned out, the reason why it doesn't work with AIO is that flock is used instead of lockf. According to the code comments, the class AIOFileLockNodeManager had been added due to a GFS2 bug, https://bugzilla.redhat.com/show_bug.cgi?id=678585. But that GFS2 bug has already been fixed more than 5 years ago, end of 2011. So I think it would be time to remove the flock-based workaround.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)