diff options
author | Xavi Hernandez <xhernandez@redhat.com> | 2018-10-31 12:26:43 +0100 |
---|---|---|
committer | Shyamsundar Ranganathan <srangana@redhat.com> | 2018-11-29 15:31:39 +0000 |
commit | 73f586a007dcffc9692f5f6be3a512a31c4a31ce (patch) | |
tree | ddb22b574bf126ef17cc215ffb763c076b169103 /README.md | |
parent | 2436286634e069639975f7b5c973f859a87de233 (diff) |
cluster/ec: prevent infinite loop in self-heal full
There was a problem in commit 7f81067 that caused infinite loop when
full heal was triggered.
The previous commit was made to prevent self-heal to go idle after a
replace brick operation. One of the changes consisted on setting a
flag to force an immediate scan of the dirty directory if a heal on
a directory succeeded (assuming it could have generated newer entries).
However that change was causing an issue with a full self-heal, since
every time an already healed directory was checked and it returned
suceessfully, it was also setting the flag, forcing self-heal to start
over again.
This patch fixes this issue by only setting the flag if the heal is not
full. It's assumed that a full self-heal will already traverse all
entries automatically, so there's no need to force a new scan later.
>Change-Id: Id12dbfc04e622b18183e796cc6cc87ccc30a6d55
>fixes: bz#1636631
>Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>
(cherry picked from commit 7150c51ad75ccba22045a35fc31e5037612d1ad4)
Change-Id: Id12dbfc04e622b18183e796cc6cc87ccc30a6d55
fixes: bz#1651525
Signed-off-by: Xavi Hernandez <xhernandez@redhat.com>
Diffstat (limited to 'README.md')
0 files changed, 0 insertions, 0 deletions