Bug 1292945

Summary:	[tiering]: cluster.tier-max-files option in tiering is not honored
Product:	[Community] GlusterFS	Reporter:	Dan Lambright <dlambrig>
Component:	tiering	Assignee:	Dan Lambright <dlambrig>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	medium	Docs Contact:
Priority:	high
Version:	3.7.6	CC:	bugs, byarlaga, hgowtham, kramdoss, nchilaka, sankarshan
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.7.7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1292671	Environment:
Last Closed:	2016-04-19 07:51:26 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:	1291152, 1292671
Bug Blocks:

Comment 1 Vijay Bellur 2015-12-18 19:32:25 UTC

REVIEW: http://review.gluster.org/13004 (cluster/tier: fix tier-max-files bookeeping and help) posted (#1) for review on release-3.7 by Dan Lambright (dlambrig)

Comment 2 Vijay Bellur 2015-12-20 13:22:14 UTC

COMMIT: http://review.gluster.org/13004 committed in release-3.7 by Dan Lambright (dlambrig) 
------
commit abf6196e1faa00a83fc0dc26150f55ca275131a9
Author: Dan Lambright <dlambrig>
Date:   Tue Dec 15 19:30:45 2015 -0500

    cluster/tier: fix tier-max-files bookeeping and help
    
    The option tier-max-files represents the maximum number
    of files trasferred by a node in a gives cycle. Fix help message
    to reflect the "per node" aspect. The code transferred one
    more file per cycle than the given value.
    
    Also change the default values of max file and max bytes to
    very large values, effectively we will not throttle migration
    unless the administrator requests it via CLI.
    
    This is a backport of 12984.
    
    > Change-Id: Ic2949ed3d8c35afe7c9ae4db72195603cfb2e28f
    > BUG: 1292671
    > Signed-off-by: Dan Lambright <dlambrig>
    > Reviewed-on: http://review.gluster.org/12984
    > Tested-by: NetBSD Build System <jenkins.org>
    > Tested-by: Gluster Build System <jenkins.com>
    Signed-off-by: Dan Lambright <dlambrig>
    
    Change-Id: Ibb234976f912ff4b20e894f2984c63792acfe814
    BUG: 1292945
    Reviewed-on: http://review.gluster.org/13004
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: Dan Lambright <dlambrig>
    Tested-by: Dan Lambright <dlambrig>

Comment 3 Kaushal 2016-04-19 07:51:26 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.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