Bug 1405165 - Allow user to disable mem-pool
Summary: Allow user to disable mem-pool
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jeff Darcy
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-15 18:27 UTC by Jeff Darcy
Modified: 2017-03-06 17:39 UTC (History)
4 users (show)

Fixed In Version: glusterfs-3.10.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-06 17:39:54 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Jeff Darcy 2016-12-15 18:27:32 UTC 
It's almost never good for performance/scalability, and sometimes it's catastrophic.  In the interest of backward compatibility the default is still to use mem-pool, but it can be disabled via a configure option.
Comment 1 Worker Ant 2016-12-15 18:29:25 UTC 
REVIEW: http://review.gluster.org/16148 (core: Disable the memory pooler in Gluster via a build flag) posted (#1) for review on master by Jeff Darcy (jdarcy)
Comment 2 Worker Ant 2017-01-03 20:30:36 UTC 
REVIEW: http://review.gluster.org/16148 (core: Disable the memory pooler in Gluster via a build flag) posted (#2) for review on master by Jeff Darcy (jdarcy)
Comment 3 Worker Ant 2017-01-03 20:31:50 UTC 
REVIEW: http://review.gluster.org/16148 (core: Disable the memory pooler in Gluster via a build flag) posted (#3) for review on master by Jeff Darcy (jdarcy)
Comment 4 Worker Ant 2017-01-04 11:42:45 UTC 
COMMIT: http://review.gluster.org/16148 committed in master by Shyamsundar Ranganathan (srangana) 
------
commit 6e4cb07d0df06a8c168394880a18a0ba4034c06b
Author: Shreyas Siravara <sshreyas>
Date:   Thu Dec 15 09:06:00 2016 -0800

    core: Disable the memory pooler in Gluster via a build flag
    
    Summary:
    Passing --disable-mempool to configure will disable the mempool.
    
    Change-Id: I60d5f70d54de507fe9f4695d7589f7ae1ba4bb0f
    BUG: 1405165
    Signed-off-by: Shreyas Siravara <sshreyas>
    Reviewed-on: http://review.gluster.org/16148
    Smoke: Gluster Build System <jenkins.org>
    Tested-by: Jeff Darcy <jdarcy>
    Reviewed-by: Niels de Vos <ndevos>
    Reviewed-by: Kaleb KEITHLEY <kkeithle>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Anoop C S <anoopcs>
    NetBSD-regression: NetBSD Build System <jenkins.org>
Comment 5 Shyamsundar 2017-03-06 17:39:54 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.10.0, please open a new bug report.

glusterfs-3.10.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://lists.gluster.org/pipermail/gluster-users/2017-February/030119.html
[2] https://www.gluster.org/pipermail/gluster-users/
Note You need to log in before you can comment on or make changes to this bug.