Bug 1216187 - readdir-ahead needs to be enabled by default for new volumes on gluster-3.7
Summary: readdir-ahead needs to be enabled by default for new volumes on gluster-3.7
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
Assignee: Satish Mohan
QA Contact:
URL:
Whiteboard:
Depends On: 1096614 1096616
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-28 17:23 UTC by Anand Nekkunti
Modified: 2016-06-16 12:56 UTC (History)
11 users (show)

Fixed In Version: glusterfs-3.8rc2
Doc Type: Bug Fix
Doc Text:
Clone Of: 1096614
: 1217135 (view as bug list)
Environment:
Last Closed: 2016-06-16 12:56:44 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Anand Avati 2015-04-28 17:51:47 UTC
REVIEW: http://review.gluster.org/10433 (glusterd: Enable readdir-ahead by default on new volumes) posted (#1) for review on master by Anand Nekkunti (anekkunt)

Comment 2 Anand Avati 2015-04-29 08:59:24 UTC
REVIEW: http://review.gluster.org/10433 (glusterd: Enable readdir-ahead by default on new volumes) posted (#2) for review on master by Anand Nekkunti (anekkunt)

Comment 3 Anand Avati 2015-05-04 12:42:16 UTC
COMMIT: http://review.gluster.org/10433 committed in master by Kaushal M (kaushal) 
------
commit 2aceadae902e6f45e02afa62ee7831479d23b4a5
Author: anand <anekkunt>
Date:   Tue Apr 28 22:42:14 2015 +0530

    glusterd: Enable readdir-ahead by default on new volumes
    
    With gluster-3.7, 'performance.readdir-ahead' will be enabled by default on
    new volumes when the cluster op-version supports it.
    
    Change-Id: I44e76a69e7d1c11e6dfad72c941caf887bb810ee
    BUG: 1216187
    Signed-off-by: anand <anekkunt>
    Reviewed-on: http://review.gluster.org/10433
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Atin Mukherjee <amukherj>
    Reviewed-by: Gaurav Kumar Garg <ggarg>
    Reviewed-by: Kaushal M <kaushal>

Comment 7 Niels de Vos 2016-06-16 12:56:44 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.