diff options
| author | Ashish Pandey <aspandey@redhat.com> | 2016-08-22 16:03:13 +0530 |
|---|---|---|
| committer | Xavier Hernandez <xhernandez@datalab.es> | 2016-09-15 23:26:28 -0700 |
| commit | 660ca23dee3a0f1a7128d3777589467b27af514b (patch) | |
| tree | 350f67cb304335721434a218fcb8a8d16d32b6e4 /tests/cluster.rc | |
| parent | e3494a0e043f83c39b865419034bd9ab980fd3a6 (diff) | |
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@redhat.com>
Reviewed-on: http://review.gluster.org/13733
Tested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>
Smoke: Gluster Build System <jenkins@build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Xavier Hernandez <xhernandez@datalab.es>
Diffstat (limited to 'tests/cluster.rc')
0 files changed, 0 insertions, 0 deletions