Bug 1283757

1) EC Selfheal traffic heats the file, as CTR Xlator is not distinguishing normal read-write FOP traffic from EC Sefheal FOP Traffic. Solution for this is detect the client-pid set in the FOP frame and ignore these FOPS in CTR Xlator. Need info from the EC dev Team, on the which client-pid EC Selfheal daemon uses to mark the FOPS different from regular FOPS.  

2) During a normal write the file gets heated up for read also, which is not correct and has performance cost w.r.t the extra updates to the database.  Well the reason for this is that each write that comes from the user to EC xlator converts to a read-modify-update FOPS. This read FOP doesnt have any marker on it to differentiate it from the regular read, and thus CTR tends to heat up the file.
Would require a marker on this read FOP or any such internal FOPs from EC xlator.

REVIEW: http://review.gluster.org/12668 (cluster/ec: Mark self-heal fops as internal) posted (#1) for review on release-3.7 by Pranith Kumar Karampuri (pkarampu)

REVIEW: http://review.gluster.org/12669 (cluster/ec: Mark internal fops appropriately) posted (#1) for review on release-3.7 by Pranith Kumar Karampuri (pkarampu)

COMMIT: http://review.gluster.org/12669 committed in release-3.7 by Xavier Hernandez (xhernandez) 
------
commit 3748b6540d7704116cbbef08b7401bdc997464cd
Author: Xavier Hernandez <xhernandez>
Date:   Tue Nov 17 14:06:20 2015 +0100

    cluster/ec: Mark internal fops appropriately
    
    1) Mark read fops in read-modify-write by EC as internal.
    2) Handle uid/gid set/reset correctly
    
     >BUG: 1282761
     >Change-Id: I5c1ce0cd6213367eaead5fed33aa2397c4e46df7
     >Signed-off-by: Xavier Hernandez <xhernandez>
     >Reviewed-on: http://review.gluster.org/12599
     >Tested-by: Gluster Build System <jenkins.com>
     >Tested-by: NetBSD Build System <jenkins.org>
     >Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    
    BUG: 1283757
    Change-Id: I9f039cf3ec6351525fb65381bad44d986595844f
    Signed-off-by: Xavier Hernandez <xhernandez>
    Reviewed-on: http://review.gluster.org/12669
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>

REVIEW: http://review.gluster.org/12668 (cluster/ec: Mark self-heal fops as internal) posted (#2) for review on release-3.7 by Pranith Kumar Karampuri (pkarampu)

COMMIT: http://review.gluster.org/12668 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) 
------
commit 9504c104d16856095ee99180d38aef02e51b0d60
Author: Pranith Kumar K <pkarampu>
Date:   Tue Nov 17 17:01:47 2015 +0530

    cluster/ec: Mark self-heal fops as internal
    
     >Change-Id: I8ae7af266d3e00460f0cfdc9389a926e5f2fee36
     >BUG: 1282761
     >Signed-off-by: Pranith Kumar K <pkarampu>
     >Reviewed-on: http://review.gluster.org/12598
     >Tested-by: Gluster Build System <jenkins.com>
     >Tested-by: NetBSD Build System <jenkins.org>
     >Reviewed-by: Xavier Hernandez <xhernandez>
    
    BUG: 1283757
    Change-Id: Ic20d4ee031265305db1a6ed2cf591ce94b7d0749
    Signed-off-by: Pranith Kumar K <pkarampu>
    Reviewed-on: http://review.gluster.org/12668
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>

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

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.9, please open a new bug report.

glusterfs-3.7.9 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://www.gluster.org/pipermail/gluster-users/2016-March/025922.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.7, please open a new bug report.

glusterfs-3.7.7 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://www.gluster.org/pipermail/gluster-users/2016-February/025292.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user