[Bugs] [Bug 1338501] implement meta-lock/unlock for lock migration
bugzilla at redhat.com
bugzilla at redhat.com
Mon Jun 6 06:33:57 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1338501
--- Comment #4 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/14462 committed in release-3.8 by Raghavendra
G (rgowdapp at redhat.com)
------
commit 3682513827f0f61fac51fd49d69b1807401a9b77
Author: Susant Palai <spalai at redhat.com>
Date: Fri Apr 22 15:20:39 2016 +0530
posix/lock: implement meta-lock/unlock functionality
problem : The lock state needs to be protected when rebalance is reading
the
lock state on the source. Otherwise there will be locks left unmigrated.
Hence, to synchronize incoming lock requests with lock-migration, meta lock
is needed. Any new lock request will be queued if there is an active
meta-lock
and with sucessful lock migration, will be unwound with EREMOTE, so that
dht module can wind the request to the correct destination.
On a successful lock migration, "pl_inode->migrated" flag is enabled.
Hence,
any further request would be unwound with EREMOTE and will be redirected to
new destination.
More details can be found here:
https://github.com/gluster/glusterfs-specs/blob/master/accepted/Lock-Migration.md
design discussion:
https://www.gluster.org/pipermail/gluster-devel/2016-January/048088.html
Change-Id: Ief033d5652b5ca4ba6f499110a521cae283d6aba
BUG: 1338501
Signed-off-by: Susant Palai <spalai at redhat.com>
Reviewed-on: http://review.gluster.org/14462
Tested-by: Kotresh HR <khiremat at redhat.com>
Smoke: Gluster Build System <jenkins at build.gluster.com>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
Reviewed-by: Raghavendra G <rgowdapp at redhat.com>
CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=HMPJJIn0TW&a=cc_unsubscribe
More information about the Bugs
mailing list