[Bugs] [Bug 1054694] A replicated volume takes too much to come online when one server is down

bugzilla at redhat.com bugzilla at redhat.com
Wed Apr 27 07:35:22 UTC 2016


--- Comment #14 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/11113 committed in master by Pranith Kumar
Karampuri (pkarampu at redhat.com) 
commit 3c35329feb4dd479c9e4856ee27fa4b12c708db2
Author: Ravishankar N <ravishankar at redhat.com>
Date:   Wed Dec 23 13:49:14 2015 +0530

    afr: propagate child up event after timeout

    Problem: During mount, afr waits for response from all its children before
    notifying the parent xlator. In a 1x2 replica volume , if one of the nodes
    down, the mount will hang for more than a minute until child down is
    from the client xlator for that node.

    When parent up is received by afr, start a 10 second timer. In the timer
    back, if we receive a successful child up from atleast one brick, propagate
    event to the parent xlator.

    Change-Id: I31e57c8802c1a03a4a5d581ee4ab82f3a9c8799d
    BUG: 1054694
    Signed-off-by: Ravishankar N <ravishankar at redhat.com>
    Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
    Reviewed-on: http://review.gluster.org/11113
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.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=k6Sd6Xrr0f&a=cc_unsubscribe

More information about the Bugs mailing list