[Bugs] [Bug 1414287] repeated operation failed warnings in gluster mount logs with disperse volume

bugzilla at redhat.com bugzilla at redhat.com
Fri Feb 24 15:51:00 UTC 2017


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



--- Comment #17 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/16468 committed in master by Pranith Kumar
Karampuri (pkarampu at redhat.com) 
------
commit c1fc1fc9cb5a13e6ddf8c9270deb0c7609333540
Author: Pranith Kumar K <pkarampu at redhat.com>
Date:   Wed Jan 25 15:31:44 2017 +0530

    cluster/ec: Don't trigger data/metadata heal on Lookups

    Problem-1
    If Lookup which doesn't take any locks observes version mismatch it can't
be
    trusted. If we launch a heal based on this information it will lead to
    self-heals which will affect I/O performance in the cases where Lookup is
    wrong. Considering self-heal-daemon and operations on the inode from client
    which take locks can still trigger heal we can choose to not attempt a heal
on
    Lookup.

    Problem-2:
    Fixed spurious failure of
    tests/bitrot/bug-1373520.t
    For the issues above, what was happening was that ec_heal_inspect()
    is preventing 'name' heal to happen

    Problem-3:
    tests/basic/ec/ec-background-heals.t
    To be honest I don't know what the problem was, while fixing
    the 2 problems above, I made some changes to ec_heal_inspect() and
    ec_need_heal() after which when I tried to recreate the spurious
    failure it just didn't happen even after a long time.

    BUG: 1414287
    Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
    Change-Id: Ife2535e1d0b267712973673f6d474e288f3c6834
    Reviewed-on: https://review.gluster.org/16468
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Xavier Hernandez <xhernandez at datalab.es>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Ashish Pandey <aspandey 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=PsngEgldnP&a=cc_unsubscribe


More information about the Bugs mailing list