[Bugs] [Bug 1176756] glusterd: remote locking failure when multiple synctask transactions are run
bugzilla at redhat.com
bugzilla at redhat.com
Thu Feb 26 12:00:37 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1176756
--- Comment #6 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/9328 committed in release-3.6 by Raghavendra
Bhat (raghavendra at redhat.com)
------
commit a1d9f01b28267fc333aebc49cb81ee69dc2c24f8
Author: Atin Mukherjee <amukherj at redhat.com>
Date: Fri Dec 12 07:21:19 2014 +0530
glusterd: Maintain per transaction xaction_peers list in syncop & mgmt_v3
In current implementation xaction_peers list is maintained in a global
variable
(glustrd_priv_t) for syncop/mgmt_v3. This means consistency and atomicity
of
peerinfo list across transactions is not guranteed when multiple
syncop/mgmt_v3
transaction are going through.
We had got into a problem in mgmt_v3-locks.t which was failing spuriously,
the
reason for that was two volume set operations (in two different volume) was
going through simultaneouly and both of these transaction were manipulating
the
same xaction_peers structure which lead to a corrupted list. Because of
which in
some cases unlock request to peer was never triggered and we end up with
having
stale locks.
Solution is to maintain a per transaction local xaction_peers list for
every
syncop.
Please note I've identified this problem in op-sm area as well and a
separate
patch will be attempted to fix it.
Finally thanks to Krishnan Parthasarathi and Kaushal M for your constant
help to
get to the root cause.
Backport URL : http://review.gluster.org/#/c/9269/
http://review.gluster.org/#/c/9422/
http://review.gluster.org/#/c/9350/
Change-Id: Ib1eaac9e5c8fc319f4e7f8d2ad965bc1357a7c63
BUG: 1176756
Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
Reviewed-on: http://review.gluster.org/9269
Tested-by: Gluster Build System <jenkins at build.gluster.com>
Reviewed-by: Kaushal M <kaushal at redhat.com>
Reviewed-on: http://review.gluster.org/9328
Reviewed-by: Raghavendra Bhat <raghavendra at redhat.com>
Tested-by: Raghavendra Bhat <raghavendra at redhat.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=zcgUqC8yYu&a=cc_unsubscribe
More information about the Bugs
mailing list