You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/08/05 13:38:00 UTC
[jira] [Commented] (ARTEMIS-2441) Use separate file for locking
broker and backup
[ https://issues.apache.org/jira/browse/ARTEMIS-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900092#comment-16900092 ]
ASF subversion and git services commented on ARTEMIS-2441:
----------------------------------------------------------
Commit f72409e38fe9a218bcc4180f41953fef2dc4c40d in activemq-artemis's branch refs/heads/master from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=f72409e ]
ARTEMIS-2441 Separate Lock Files
Certain devices or file systems won't support record level locking.
For that reason I am changing FileLockNodeManager to use separate files (one for each position) instead of using tryLock(position);
A good example for this would be cephFS where channel.tryLock or channel.tryLock works but it fails at a record level.
> Use separate file for locking broker and backup
> -----------------------------------------------
>
> Key: ARTEMIS-2441
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2441
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Affects Versions: 2.9.0
> Reporter: clebert suconic
> Assignee: clebert suconic
> Priority: Major
> Fix For: 2.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Some file systems don't support positional locking (or record level).
>
> A current example I bumped into is ceph-fs, however, I have had issues with record locking before with certain NFS versions, GFS and others.
>
> To make things better, I'm just splitting the locks to separate files, and everything should still work the same while allowing these devices to work seamless.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)