[Bugs] [Bug 1177339] entry self-heal in 3.5 and 3.6 are not compatible

[bugzilla at redhat.com]

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



--- Comment #3 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/9352 committed in release-3.5 by Niels de Vos
(ndevos at redhat.com) 
------
commit 069bc07126d32bc6319d587ff91aa0006ba5fac8
Author: Pranith Kumar K <pkarampu at redhat.com>
Date:   Fri Nov 14 14:23:31 2014 +0530

    features/locks: Add lk-owner checks in entrylk

            Backport of http://review.gluster.com/9125

    Problem:
    entry self-heal in 3.6 and above, takes full lock on the directory only for
the
    duration of figuring out the xattrs of the directories where as 3.5 takes
locks
    through out the entry-self-heal. If the cluster is heterogeneous then there
is
    a chance that 3.6 self-heal is triggered and then 3.5 self-heal will also
    triggered and both the self-heal daemons of 3.5 and 3.6 do self-heal.

    Fix in 3.6.2 and above:
    3.6.2 and above gets an entry lock on a very long name before entry
self-heal
    begins so that 3.5 entry self-heal will not get locks until 3.6.x entry
    self-heal completes. Make 3.5 locks accept nested locks from same lk-owner,
    client.

    BUG: 1177339
    Change-Id: I65d4c3732d1e074720422533f85f6e13f933ecad
    Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
    Reviewed-on: http://review.gluster.org/9352
    Reviewed-by: Krutika Dhananjay <kdhananj at redhat.com>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Niels de Vos <ndevos at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.