[Bugs] [Bug 1566352] posix-acl not synchronized between glusterfs clients

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1566352



--- Comment #1 from zhou lin <zz.sh.cynthia at gmail.com> ---
i find that after i revert change https://review.gluster.org/16945
there is no such issue.
following is my analysis on this issue.
When one client setfacl on volume root (E.g /mnt/mstate) it will update local
acl buffer and send setxattr OP request to remote glusterfs server side, other
gluster clients depend on lookup to update its local acl buffer, but in case of
volume root , I do not find any lookup operation for it, except for the first
time when client gets up. so , why there is no lookup OP for volume root dir?
If root dir is looked up just like other directory, there is no such issue,
because the lookup cbk in posix-acl will update its local acl buffer. When
other clients try to check their acl, they will send getxattr OP to local
posix-acl translator, however, this translator retrieves acl from remote
glusterfs server side instead of its local buffer, this makes user very
confused, because what they see is not its local acl buffer content! Any other
method to update all other client’s local acl buffer?
from current design it seems client will depend on some kinds of fop (E.g
lookup op to update local acl buffer) i think it is better if there is some
synchronization mechanism between clients.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.