You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently, a new jvm properties "chronicle.map.disable.locking" was managed in chronicle map to disable file locking
However, a file lock is still present during persistent file creation, even if the previous property is set ( private method fileLockedIO called in ChronicleMapBuilder class). I need to disable completely locking for CephFS system, due to this limitation : https://github.com/ceph/ceph-client/blob/664f1e259a982bf213f0cd8eea7616c89546585c/fs/locks.c
/* Don't allow mandatory locks on files that may be memory mapped and shared */
Is it possible to add this possibility in chronicle-map?
Thanks,
The text was updated successfully, but these errors were encountered:
Hi,
Recently, a new jvm properties "chronicle.map.disable.locking" was managed in chronicle map to disable file locking
However, a file lock is still present during persistent file creation, even if the previous property is set ( private method fileLockedIO called in ChronicleMapBuilder class). I need to disable completely locking for CephFS system, due to this limitation :
https://github.com/ceph/ceph-client/blob/664f1e259a982bf213f0cd8eea7616c89546585c/fs/locks.c
/* Don't allow mandatory locks on files that may be memory mapped and shared */
Is it possible to add this possibility in chronicle-map?
Thanks,
The text was updated successfully, but these errors were encountered: