Bug 1377570
| Summary: | EC: Set/unset dirty flag for all the update operations | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Ashish Pandey <aspandey> |
| Component: | disperse | Assignee: | Ashish Pandey <aspandey> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.9 | CC: | bugs, hgowtham |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 3.9.1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1316873 | Environment: | |
| Last Closed: | 2017-03-08 08:34:45 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1316873 | ||
| Bug Blocks: | 1361513 | ||
|
Description
Ashish Pandey
2016-09-20 06:33:47 UTC
REVIEW: http://review.gluster.org/15534 (cluster/ec: set/unset dirty flag for data/metadata update) posted (#1) for review on release-3.9 by Ashish Pandey (aspandey) REVIEW: http://review.gluster.org/15534 (cluster/ec: set/unset dirty flag for data/metadata update) posted (#2) for review on release-3.9 by Pranith Kumar Karampuri (pkarampu) COMMIT: http://review.gluster.org/15534 committed in release-3.9 by Pranith Kumar Karampuri (pkarampu) ------ commit f59d0c80f612413e02712ab4d8e7132b7a714d19 Author: Ashish Pandey <aspandey> 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> >Reviewed-on: http://review.gluster.org/13733 >Tested-by: Pranith Kumar Karampuri <pkarampu> >Smoke: Gluster Build System <jenkins.org> >NetBSD-regression: NetBSD Build System <jenkins.org> >CentOS-regression: Gluster Build System <jenkins.org> >Reviewed-by: Xavier Hernandez <xhernandez> Change-Id: Ide5668bdec7b937a61c5c840cdc79a967598e1e9 BUG: 1377570 Signed-off-by: Ashish Pandey <aspandey> Reviewed-on: http://review.gluster.org/15534 Reviewed-by: Pranith Kumar Karampuri <pkarampu> Tested-by: Pranith Kumar Karampuri <pkarampu> Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> |