Clarify file-lock being a distributed name lock#184
Clarify file-lock being a distributed name lock#184kwin wants to merge 1 commit intoapache:masterfrom
file-lock being a distributed name lock#184Conversation
|
Well, it is not "distributed" as is not for multi hosts case. I'd rather distinguish like ST, MT, MP/SH and MH (single thread, multi thread, multi process/single-host and multi-host). File is MP, redisson is MH in this manner. |
|
Why is it not MH if you have e.g. a NFS network share mounted? |
|
Unsure about NFS file locking... @michael-o ? |
|
Looking at https://www.freebsd.org/cgi/man.cgi?query=nfsv4&sektion=4&manpath=FreeBSD+9.0-RELEASE NFSv4 has advisory locks. Forget 3 or older. Now there many impls of it and I don't know its quality. I don't have a v4 server at hand. Expect it to work, but your kilometrage may vary. So I am not rejecting it on v4. |
|
Ceph and friends, no idea. |
|
That was my thought as well: only NFSv4 w/ all the services needed (so not "bare" nfs server, but all rpc and whistles and bells needed) |
Correct, no blanket v4. |
|
In short: if your FS correctly support locking, should work. Local FS usually is okay. For NFS your mileage may vary. |
|
This should also go to the docs. |
|
Superseded by #185 |
3 participants
No description provided.