[Bugs] [Bug 1464359] selfheal deamon cpu consumption not reducing when IOs are going on and all redundant bricks are brought down one after another

[bugzilla at redhat.com]

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



--- Comment #4 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17692 committed in master by Xavier
Hernandez (xhernandez at datalab.es) 
------
commit 0ae38df6403942a2438404d46a6e05b503db3485
Author: Ashish Pandey <aspandey at redhat.com>
Date:   Tue Jul 4 16:18:20 2017 +0530

    cluster/ec : Don't try to heal when no sink is UP

    Problem:
    4 + 2 EC volume configuration.
    If untar of linux is going on and we kill a brick,
    indices will be created for the files/dir which need
    to be healed. ec_shd_index_sweep spawns threads to
    scan these entries and start heal. If in the middle
    of this we kill one more brick, we end up in a
    situation where we can not heal an entry as there
    are only "ec->fragment" number of bricks are UP.
    However, the scan will be continued and it will
    trigger the heal for those entries.

    Solution:
    When a heal is triggered for an entry, check if it
    *CAN* be healed or not. If not come out with ENOTCONN.

    Change-Id: I305be7701c289f36bd7bde22491b71074771424f
    BUG: 1464359
    Signed-off-by: Ashish Pandey <aspandey at redhat.com>
    Reviewed-on: https://review.gluster.org/17692
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
    Reviewed-by: Sunil Kumar Acharya <sheggodu at redhat.com>
    Reviewed-by: Xavier Hernandez <xhernandez at datalab.es>

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