REVIEW: http://review.gluster.org/13849 (cluster/ec: Rebalance hangs during rename) posted (#1) for review on release-3.7 by Ashish Pandey (aspandey)
COMMIT: http://review.gluster.org/13849 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) ------ commit 3d34c495d547866a533bc0614b14163381830095 Author: Ashish Pandey <aspandey> Date: Wed Feb 17 15:57:02 2016 +0530 cluster/ec: Rebalance hangs during rename Problem: During the rename of a particular file (ec is holding blocking inodelk on the parent directory), if the rename of another file under the same directory comes. EC does not release the lock and goes ahead and renames the "new" file with the "already held lock". That causes rebalance process to be blocked on a lock which has been acquired by rename. Solution: While rename fop comes, ec takes blocking inodelk on old and new parent of the file. Before releasing, every lock held by ec, it waits for some "time" to see if that lock can be reused by the next fop. If within this "time" some other request comes, it releases this lock based on condition "lock count > 1" To get this "lock count" for rename fop, we have implemented "pl_rename" in feature/lock. Also, on ec side, changed the condition to release the lock based on the type of fop and old and new parent directories. master- http://review.gluster.org/#/c/13460/ Change-Id: I979dbab1185df962e8f305a6074ae1186ffe7db0 Bug: 1322299 Signed-off-by: Ashish Pandey <aspandey> Reviewed-on: http://review.gluster.org/13849 Smoke: Gluster Build System <jenkins.com> CentOS-regression: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Pranith Kumar Karampuri <pkarampu>
Change 3d34c495d547866a533bc0614b14163381830095 is being reverted from the release-3.7 branch as it breaks building packages.
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.