Description of problem: With rebalance doing the lock migration, the locks on destination will have client information of rebalance in the posix_lock_t structure. Hence, flush on the destination will not be able to identify any locks to delete. And future conflicting lock requests will not be granted. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/14286 (posix/locks: make flush work on new destination) posted (#2) for review on master by Susant Palai (spalai)
REVIEW: http://review.gluster.org/14286 (posix/locks: make flush work on new destination) posted (#3) for review on master by Susant Palai (spalai)
REVIEW: http://review.gluster.org/14286 (posix/locks: make flush work on new destination) posted (#4) for review on master by Susant Palai (spalai)
REVIEW: http://review.gluster.org/14286 (posix/locks: make flush work on new destination) posted (#5) for review on master by Susant Palai (spalai)
REVIEW: http://review.gluster.org/14286 (posix/locks: make flush work on new destination) posted (#6) for review on master by Susant Palai (spalai)
Marking as DEFERRED to indicate the status. Will revisit after couple of months to check if this is critical.