[
https://issues.apache.org/jira/browse/ARTEMIS-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965935#comment-15965935
]
ASF GitHub Bot commented on ARTEMIS-1108:
-----------------------------------------
Github user clebertsuconic commented on the issue:
https://github.com/apache/activemq-artemis/pull/1194
@bgutjahr I'm happy to let this locker go if locking works now.
This was a hack to go around the GFS2 bug. Now it can go freely 👍
> 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
>
> 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)
