Bug 1336152

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

Comment 1 Vijay Bellur 2016-05-14 22:12:47 UTC

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

Comment 2 Vijay Bellur 2016-05-18 20:04:37 UTC

COMMIT: http://review.gluster.org/14342 committed in release-3.8 by Dan Lambright (dlambrig) 
------
commit 77591f4ddc1bfb5dd846314aff5dbee37ca590d2
Author: Joseph Fernandes <josferna>
Date:   Tue May 10 21:10:08 2016 +0530

    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: I08cc92db1fb8d48026ca51743be6cafe385d1b79
    BUG: 1336152
    Reviewed-on: http://review.gluster.org/14342
    Smoke: Gluster Build System <jenkins.com>
    Reviewed-by: Joseph Fernandes
    Tested-by: Dan Lambright <dlambrig>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>

Comment 3 Niels de Vos 2016-06-16 14:06:29 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.8.0, please open a new bug report.

glusterfs-3.8.0 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] http://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user