[Bugs] [Bug 1636631] Issuing a "heal ... full" on a disperse volume causes permanent high CPU utilization.

bugzilla at redhat.com bugzilla at redhat.com
Wed Oct 31 11:50:19 UTC 2018


--- Comment #2 from Xavi Hernandez <jahernan at redhat.com> ---
I've found the problem. Currently, when a directory is healed, a flag is set
that forces heal to be retried. This is necessary after a replace brick because
after healing a directory, new entries to be healed could appear (the only bad
entry just after a replace brick is the root directory). In this case, a new
iteration of the heal process will immediately take those new entries and heal
them, instead of going idle after completing a full sweep of the (previous)
list of bad entries.

However this approach on a full self-heal causes it to run endless. First it
tries to heal the root directory, which succeeds. This causes the flag to be
set, even if no entries have been really added to be healed.

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

More information about the Bugs mailing list