[Bugs] [Bug 1173414] glusterd: remote locking failure when multiple synctask transactions are run

bugzilla at redhat.com bugzilla at redhat.com
Tue Dec 23 04:14:19 UTC 2014


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



--- Comment #6 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/9269 committed in master by Kaushal M
(kaushal at redhat.com) 
------
commit da9deb54df91dedc51ebe165f3a0be646455cb5b
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.

    Change-Id: Ib1eaac9e5c8fc319f4e7f8d2ad965bc1357a7c63
    BUG: 1173414
    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>

-- 
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=NGZenJhrHR&a=cc_unsubscribe


More information about the Bugs mailing list