[Bugs] [Bug 1399989] [Disperse] healing should not start if only data bricks are UP
bugzilla at redhat.com
bugzilla at redhat.com
Thu Dec 22 05:43:23 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1399989
--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: http://review.gluster.org/15974 committed in release-3.9 by Pranith
Kumar Karampuri (pkarampu at redhat.com)
------
commit 63c6eafac95fbeb126fbc168933f4f204ea0a0ec
Author: Ashish Pandey <aspandey at redhat.com>
Date: Mon Nov 28 13:42:33 2016 +0530
cluster/ec: Healing should not start if only "data" bricks are UP
Problem: In a disperse volume with "K+R" configuration, where
"K" is the number of data bricks and "R" is the number of redundancy
bricks (Total number of bricks, N = K+R), if only K bricks are UP,
we should NOT start heal process. This is because the bricks, which
are supposed to be healed, are not UP. This will unnecessary
eat up the resources.
Solution: Check for the number of xl_up_count and only
if it is greater than ec->fragments (number of data bricks),
start heal process.
>Change-Id: I8579f39cfb47b65ff0f76e623b048bd67b15473b
>BUG: 1399072
>Signed-off-by: Ashish Pandey <aspandey at redhat.com>
>Reviewed-on: http://review.gluster.org/15937
>Reviewed-by: Xavier Hernandez <xhernandez at datalab.es>
>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>
>Signed-off-by: Ashish Pandey <aspandey at redhat.com>
Change-Id: I8579f39cfb47b65ff0f76e623b048bd67b15473b
BUG: 1399989
Signed-off-by: Ashish Pandey <aspandey at redhat.com>
Reviewed-on: http://review.gluster.org/15974
Smoke: Gluster Build System <jenkins at build.gluster.org>
Reviewed-by: Xavier Hernandez <xhernandez at datalab.es>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
--
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=Mzz74YdhxN&a=cc_unsubscribe
More information about the Bugs
mailing list