Bug 1336148

Summary:	[Tiering]: Files remain in hot tier even after detach tier completes
Product:	[Community] GlusterFS	Reporter:	Dan Lambright <dlambrig>
Component:	tiering	Assignee:	sankarshan <sankarshan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.7.11	CC:	bugs, kramdoss, nbalacha, rcyriac, rhinduja, sankarshan
Target Milestone:	---	Keywords:	Regression, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.12	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1334234	Environment:
Last Closed:	2016-06-28 12:17:59 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:	1334234, 1336152
Bug Blocks:	1311817, 1334839

Comment 1 Vijay Bellur 2016-05-14 21:57:02 UTC

REVIEW: http://review.gluster.org/14341 (tier/detach: Clear tier-fix-layout-complete xattr after migration threads join) posted (#1) for review on release-3.7 by Dan Lambright (dlambrig)

Comment 2 Vijay Bellur 2016-05-16 12:22:00 UTC

COMMIT: http://review.gluster.org/14341 committed in release-3.7 by Dan Lambright (dlambrig) 
------
commit c6355e1dbf02c1d06f2d7b01633fbc3fb13500b7
Author: Dan Lambright <dlambrig>
Date:   Sat May 14 17:51:44 2016 -0400

    tier/detach: Clear tier-fix-layout-complete xattr after migration threads join
    
    Previously we had wrongly placed the clearing tier-fix-layout-complete
    xattr before the joining of migration threads. This would lead to
    situations where failure of clearing the xattr would cause the
    premature death of migration threads.
    
    Now we clear the xattr only after the data movement threads join,
    ensuring that all migration is done.
    
    This is a backport of 14285
    
    > Change-Id: I829b671efa165ae13dbff7b00707434970b37a09
    > BUG: 1334839
    > Signed-off-by: Joseph Fernandes <josferna>
    
    Signed-off-by: Dan Lambright <dlambrig>
    
    Change-Id: I475242e6a05cacd2252dc5c29b160e7abc5d1791
    BUG: 1336148
    Reviewed-on: http://review.gluster.org/14341
    Smoke: Gluster Build System <jenkins.com>
    Tested-by: N Balachandran <nbalacha>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: N Balachandran <nbalacha>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Dan Lambright <dlambrig>

Comment 4 Kaushal 2016-06-28 12:17:59 UTC

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

glusterfs-3.7.12 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-devel/2016-June/049918.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user