Bug 1323016

REVIEW: http://review.gluster.org/13879 (tier/dht : Attach tier fix layout to run in background) posted (#1) for review on release-3.7 by Joseph Fernandes

COMMIT: http://review.gluster.org/13879 committed in release-3.7 by Dan Lambright (dlambrig) 
------
commit ff4ceab95fea5108db2d1acebfa6ea231e2845e4
Author: Joseph Fernandes <josferna>
Date:   Tue Feb 23 12:51:45 2016 +0530

    tier/dht : Attach tier fix layout to run in background
    
    1. Spawn a thread for background fix-layout for tier process.
    
    2. Once the fix-layout is completed a marker xttr is set on the root of
       volume to mark the completion of the background fixlayout, so that
       even if the tier process is spawned again, fixlayout will not be
       issued, if it was completed last time.
    
    3. Please note that promotion of legacy files will happen eventually as
       the ctr lookup heal in the fixlayout slowly heals the ctr db for legacy
       files OR the ctr lookup heal happend due to a name lookup.
    
    4. When a detach tier is successful in evacuation data from hot tier, we remove
       the marker xattr is removed. So that next attach tier runs the background
       tier fixlayout.
    
    what is remaining ?
    1. Instead of clearing the marker xattr of tiering fix layout at the end of detach start
       clear it during detach commit. But the issue is detach commit is a glusterd operation
       and the volume is not mounted in glusterd.
       The reason we want to do it in detach commit is that if the admin wants to attach the
       same tier again, then a background fixlayout will be triggered, which would not be needed.
    2. Clearing the CTR DB of the cold bricks when there is a detach commit, as it will be having
       entries which will be stale when the volume is used, with ctr off (ctr is switched off only when
       we have detach commit.)
    
    Backport of http://review.gluster.org/13491
    
    > Change-Id: Ibe343572e95865325cd0eef4d0b976b626a3c0c5
    > BUG: 1313228
    > Signed-off-by: Joseph Fernandes <josferna>
    > Reviewed-on: http://review.gluster.org/13491
    > Smoke: Gluster Build System <jenkins.com>
    > Tested-by: Joseph Fernandes
    > NetBSD-regression: NetBSD Build System <jenkins.org>
    > CentOS-regression: Gluster Build System <jenkins.com>
    > Reviewed-by: Dan Lambright <dlambrig>
    Signed-off-by: Joseph Fernandes <josferna>
    
    Change-Id: Ic28affdf78d2ac0f394f3dd59f0126df7915d609
    BUG: 1323016
    Reviewed-on: http://review.gluster.org/13879
    Smoke: Gluster Build System <jenkins.com>
    Reviewed-by: Joseph Fernandes
    Tested-by: Joseph Fernandes
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Dan Lambright <dlambrig>

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.11, please open a new bug report.

glusterfs-3.7.11 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-April/026321.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user