[Bugs] [Bug 1316873] EC: Set/unset dirty flag for all the update operations
bugzilla at redhat.com
bugzilla at redhat.com
Fri Sep 16 06:26:32 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1316873
--- Comment #25 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: http://review.gluster.org/13733 committed in master by Xavier Hernandez
(xhernandez at datalab.es)
------
commit 660ca23dee3a0f1a7128d3777589467b27af514b
Author: Ashish Pandey <aspandey at redhat.com>
Date: Mon Aug 22 16:03:13 2016 +0530
cluster/ec: set/unset dirty flag for data/metadata update
Currently, for all the update operations, metadata or data,
we set the dirty flag at the end of the operation only if
a brick is down. This leads to delay in healing and in some
cases not at all.
In this patch we set (+1) the dirty flag
at the start of the metadata or data update operations and
after successfull completion of the fop, we unset (-1) it again.
Change-Id: Ide5668bdec7b937a61c5c840cdc79a967598e1e9
BUG: 1316873
Signed-off-by: Ashish Pandey <aspandey at redhat.com>
Reviewed-on: http://review.gluster.org/13733
Tested-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
Smoke: Gluster Build System <jenkins at build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
Reviewed-by: Xavier Hernandez <xhernandez at datalab.es>
--
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=0oSRqBOS23&a=cc_unsubscribe
More information about the Bugs
mailing list