Bug 1300412 - Data Tiering:Change the default tiering values to optimize tiering settings
Summary: Data Tiering:Change the default tiering values to optimize tiering settings
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: tiering
Version: mainline
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact: bugs@gluster.org
URL:
Whiteboard:
Depends On: 1283961
Blocks: 1260783 1306302
TreeView+ depends on / blocked
 
Reported: 2016-01-20 17:32 UTC by Joseph Elwin Fernandes
Modified: 2016-06-16 13:55 UTC (History)
7 users (show)

Fixed In Version: glusterfs-3.8rc2
Clone Of: 1283961
: 1306302 (view as bug list)
Environment:
Last Closed: 2016-06-16 13:55:08 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Vijay Bellur 2016-01-20 17:33:24 UTC
REVIEW: http://review.gluster.org/13270 (tier/dht : Default value for tier-demote-frequency is 3600 sec) posted (#2) for review on master by Joseph Fernandes

Comment 2 Vijay Bellur 2016-01-20 17:51:08 UTC
REVIEW: http://review.gluster.org/13270 (tier/dht : Default value for demote-freq, max files and mb) posted (#3) for review on master by Joseph Fernandes

Comment 3 Vijay Bellur 2016-01-21 02:07:29 UTC
REVIEW: http://review.gluster.org/13270 (tier/dht : Default value for demote-freq, max files and mb) posted (#4) for review on master by Joseph Fernandes

Comment 4 Vijay Bellur 2016-01-26 17:16:09 UTC
COMMIT: http://review.gluster.org/13270 committed in master by Dan Lambright (dlambrig) 
------
commit ce2c58d0fab517320059af7cea2e36e5cd246b6e
Author: Joseph Fernandes <josferna>
Date:   Wed Jan 20 22:27:33 2016 +0530

    tier/dht : Default value for demote-freq, max files and mb
    
    Default value for tier-demote-frequency is 3600 sec to avoid
    frequent demotions.
    
    Default value for tier-max-mb is 4000 mb
    
    Default value for tier-max-files is 10000 files
    
    Change-Id: Ie60951c478a7462c425059699ab82511aa13fa0a
    BUG: 1300412
    Signed-off-by: Joseph Fernandes <josferna>
    Reviewed-on: http://review.gluster.org/13270
    Smoke: Gluster Build System <jenkins.com>
    Tested-by: Dan Lambright <dlambrig>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Dan Lambright <dlambrig>

Comment 5 Niels de Vos 2016-06-16 13:55:08 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


Note You need to log in before you can comment on or make changes to this bug.