Bug 1330353

Summary:	[Tiering]: promotion of files may not be balanced on distributed hot tier when promoting files with size as that of max.mb
Product:	[Community] GlusterFS	Reporter:	Joseph Elwin Fernandes <josferna>
Component:	tiering	Assignee:	Joseph Elwin Fernandes <josferna>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	mainline	CC:	bugs, dlambrig, hgowtham, josferna, kramdoss, nchilaka, rhs-bugs, sankarshan
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1328721
Clones:	1332138 (view as bug list)		Environment:
Last Closed:	2016-06-16 14:04:21 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:	1328721
Bug Blocks:	1332138

Comment 1 Vijay Bellur 2016-04-26 00:50:53 UTC

REVIEW: http://review.gluster.org/14068 (tier/migrator: Fetch the next query file for the next cycle) posted (#1) for review on master by Joseph Fernandes

Comment 2 Vijay Bellur 2016-04-27 00:09:45 UTC

REVIEW: http://review.gluster.org/14068 (tier/migrator: Fetch the next query file for the next cycle) posted (#2) for review on master by Joseph Fernandes

Comment 3 Vijay Bellur 2016-04-27 00:13:18 UTC

REVIEW: http://review.gluster.org/14068 (tier/migrator: Fetch the next query file for the next cycle) posted (#3) for review on master by Joseph Fernandes

Comment 4 Vijay Bellur 2016-04-30 14:30:53 UTC

COMMIT: http://review.gluster.org/14068 committed in master by Dan Lambright (dlambrig) 
------
commit 0d23f5207337fa54be57939eb8d70fe835d4658b
Author: Joseph Fernandes <josferna>
Date:   Tue Apr 26 06:10:16 2016 +0530

    tier/migrator: Fetch the next query file for the next cycle
    
    Problem: When we spawn promote and demote thread, query files
    are build. And only query file with index 0 is picked for migration
    as the first query file. This may not be suitable for scenarios,
    where the file in the query are too big to move in the first cycle,
    as a result file in the other query files always get missed. We need to
    shuffle so that other query files also get a chance.
    
    Fix: Remember the previous first query file and shift it by one index,
    before the migration starts.
    
    Change-Id: I704947bcf4bab6b20b1179a6d9ae4a15a3d51bd9
    BUG: 1330353
    Signed-off-by: Joseph Fernandes <josferna>
    Reviewed-on: http://review.gluster.org/14068
    Tested-by: Joseph Fernandes
    Smoke: Gluster Build System <jenkins.com>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Dan Lambright <dlambrig>
    Tested-by: Dan Lambright <dlambrig>
    NetBSD-regression: NetBSD Build System <jenkins.org>

Comment 5 Niels de Vos 2016-06-16 14:04:21 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