[Bugs] [Bug 1361513] New: EC: Set/unset dirty flag for all the update operations

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1361513

            Bug ID: 1361513
           Summary: EC: Set/unset dirty flag for all the update operations
           Product: Red Hat Gluster Storage
           Version: 3.1
         Component: disperse
          Keywords: Triaged
          Severity: medium
          Priority: medium
          Assignee: pkarampu at redhat.com
          Reporter: pkarampu at redhat.com
        QA Contact: storage-qa-internal at redhat.com
                CC: aspandey at redhat.com, bugs at gluster.org,
                    hgowtham at redhat.com, rhs-bugs at redhat.com
        Depends On: 1316873



+++ This bug was initially created as a clone of Bug #1316873 +++

Description of problem:

Set/unset dirty flag for all the update operations

If write operation come for a file, set its the dirty flag in preop for that
file, perform write and then unset dirty flag in post of if write is successful
on all the bricks. 
If any brick goes down during write fop, keep the dirty flag ON and don't unset
it in postop. This will trigger heal for the file when the bricks comes up.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Vijay Bellur on 2016-03-15 03:26:03 EDT ---

REVIEW: http://review.gluster.org/13733 (cluster/ec: set/unset dirty flag for
data/metadata update) posted (#1) for review on master by Ashish Pandey
(aspandey at redhat.com)

--- Additional comment from Vijay Bellur on 2016-03-16 02:48:54 EDT ---

REVIEW: http://review.gluster.org/13733 (cluster/ec: set/unset dirty flag for
data/metadata update) posted (#2) for review on master by Ashish Pandey
(aspandey at redhat.com)

--- Additional comment from Vijay Bellur on 2016-03-21 01:45:56 EDT ---

REVIEW: http://review.gluster.org/13733 (cluster/ec: set/unset dirty flag for
data/metadata update) posted (#3) for review on master by Ashish Pandey
(aspandey at redhat.com)

--- Additional comment from Vijay Bellur on 2016-03-21 02:24:13 EDT ---

REVIEW: http://review.gluster.org/13733 (cluster/ec: set/unset dirty flag for
data/metadata update) posted (#4) for review on master by Ashish Pandey
(aspandey at redhat.com)

--- Additional comment from Vijay Bellur on 2016-03-21 05:40:30 EDT ---

REVIEW: http://review.gluster.org/13733 (cluster/ec: set/unset dirty flag for
data/metadata update) posted (#5) for review on master by Ashish Pandey
(aspandey at redhat.com)

--- Additional comment from Mike McCune on 2016-03-28 18:17:27 EDT ---

This bug was accidentally moved from POST to MODIFIED via an error in
automation, please see mmccune at redhat.com with any questions

--- Additional comment from Vijay Bellur on 2016-04-04 04:13:13 EDT ---

REVIEW: http://review.gluster.org/13733 (cluster/ec: set/unset dirty flag for
data/metadata update) posted (#6) for review on master by Ashish Pandey
(aspandey at redhat.com)

--- Additional comment from Vijay Bellur on 2016-04-12 13:55:49 EDT ---

REVIEW: http://review.gluster.org/13733 (cluster/ec: set/unset dirty flag for
data/metadata update) posted (#7) for review on master by Ashish Pandey
(aspandey at redhat.com)

--- Additional comment from Vijay Bellur on 2016-04-19 16:41:28 EDT ---

REVIEW: http://review.gluster.org/13733 (cluster/ec: set/unset dirty flag for
data/metadata update) posted (#8) for review on master by Ashish Pandey
(aspandey at redhat.com)


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1316873
[Bug 1316873] EC: Set/unset dirty flag for all the update operations
-- 
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=6cvLDMtejB&a=cc_unsubscribe