[Bugs] [Bug 1396880] refresh-config fails and crashes ganesha when mdcache is enabled on the volume.

[bugzilla at redhat.com]

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



--- Comment #3 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: http://review.gluster.org/15890 committed in release-3.9 by Pranith
Kumar Karampuri (pkarampu at redhat.com) 
------
commit c35cb76498749d7d34ebb8134f5780fe060d789d
Author: Poornima G <pgurusid at redhat.com>
Date:   Fri Oct 28 15:27:15 2016 +0530

    afr,dht,ec: Replace GF_EVENT_CHILD_MODIFIED with event
SOME_DESCENDENT_DOWN/UP

    Backport of http://review.gluster.org/#/c/15764/

    Currently these are few events related to child_up/down:
    GF_EVENT_CHILD_UP :  Issued when any of the protocol client
    connects.
    GF_EVENT_CHILD_MODIFIED : Issued by afr/dht/ec
    GF_EVENT_CHILD_DOWN : Issued when any of the protocol client
    disconnects.
    These events get modified at the dht/afr/ec layers. Here is a
    brief on the same.

    DHT:
    - All the subvolumes reported once, and atleast one child came
      up, then GF_EVENT_CHILD_UP is issued
    - connect GF_EVENT_CHILD_UP is issued
    - disconnect GF_EVENT_CHILD_MODIFIED is issued
    - All the subvolumes disconnected, GF_EVENT_CHILD_DOWN is issued

    AFR:
    - First subvolume came up, then GF_EVENT_CHILD_UP is issued
    - Subsequent subvolumes coming up, results in GF_EVENT_CHILD_MODIFIED
    - Any of the subvolumes go down, then GF_EVENT_SOME_CHILD_DOWN is issued
    - Last up subvolume goes down, then GF_EVENT_CHILD_DOWN is issued

    Until the patch [1] introduced GF_EVENT_SOME_CHILD_UP,
    GF_EVENT_CHILD_MODIFIED was issued by afr/dht when any of the subvolumes
    go up or down.

    Now with md-cache changes, there is a necessity to differentiate between
    child up and down. Hence, introducing GF_EVENT_SOME_DESCENDENT_DOWN/UP and
    getting rid of GF_EVENT_CHILD_MODIFIED.

    [1] http://review.gluster.org/12573

    >Reviewed-on: http://review.gluster.org/15764
    >CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    >NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    >Smoke: Gluster Build System <jenkins at build.gluster.org>
    >Reviewed-by: N Balachandran <nbalacha at redhat.com>
    >Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
    >Reviewed-by: Rajesh Joseph <rjoseph at redhat.com>
    (cherry picked from commit f7ab6c45963fa0da68acedfb14281cd2456abc68)

    Change-Id: I704140b6598f7ec705493251d2dbc4191c965a58
    BUG: 1396880
    Signed-off-by: Poornima G <pgurusid at redhat.com>
    Reviewed-on: http://review.gluster.org/15890
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu 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.