[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 #2 from Ashish Pandey <aspandey at redhat.com> ---
RCA:

SHD takes care of this scenario when redundant number of bricks are down.
SHD does not trigger heal in this case.

Now consider 4+2 volume.
When a continuous IO is going on and 2 bricks are down, an update fop will find
out that the fop is not successful on 2 bricks and so it will immediately
trigger a heal. This is what client side heal does. In this case also, it is of
NO use to trigger a heal when you can not actually heal a file as 2 bricks are
down.

This is causing unnecessary CPU hogging.

Solution:

1 - While triggering a client side heal check if more than 4 bricks are UP or
not. Trigger heal accordingly.

OR

2 - Disable background heal as soon as  2 bricks go down and we can not heal.
Enable it again as soon as we see more than 4 bricks UP.

I think [1] would be a better solution which can further be improved on.
What if the brick, which requires heal, is down. Even in this case we should
not trigger heal.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.