[Bugs] [Bug 1473026] replace-brick failure leaves glusterd in inconsistent state
bugzilla at redhat.com
bugzilla at redhat.com
Thu Jul 20 09:05:29 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1473026
Ravishankar N <ravishankar at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pkarampu at redhat.com
--- Comment #4 from Ravishankar N <ravishankar at redhat.com> ---
(In reply to Atin Mukherjee from comment #3)
> Ravi,
>
> If we'd really need to fix this issue, then IMO replace brick should be
> implemented in mgmt_v3 framework as it provides a sort of rollback mechanism
> in the form of post commit phase (snapshot does use it in few areas). With
> GD2, infra for rolling back the transactions will be in place.
Okay, I think this bug can be taken in for glusterfs-4.0 using GD2. Pranith,
feel free to add your thoughts if you feel otherwise.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list