activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-1108) Shared-store with AIO fails to lock lockfile on NFS shares
Date Tue, 11 Apr 2017 16:11:41 GMT


ASF GitHub Bot commented on ARTEMIS-1108:

Github user clebertsuconic commented on the issue:
    No, NIO wouldn't work with GFS2, we were recommending libaio with GFS2.
    I would need to verify this works with GFS2 before we can merge it.

> Shared-store with AIO fails to lock lockfile on NFS shares
> ----------------------------------------------------------
>                 Key: ARTEMIS-1108
>                 URL:
>             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, 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

View raw message