Bug 1001207

Summary: cluster/stripe: make coalesce mode the default
Product: [Community] GlusterFS Reporter: Brian Foster <bfoster>
Component: stripeAssignee: Brian Foster <bfoster>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.4.0CC: gluster-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.5.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-04-17 11:46:25 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:

Description Brian Foster 2013-08-26 18:06:33 UTC
stripe/coalesce mode has been available for quite some time, enough to get any major issues shaken out. Make coalesce mode enabled by default for striped volumes.

Comment 1 Anand Avati 2013-08-26 18:08:10 UTC
REVIEW: http://review.gluster.org/5624 (cluster/stripe: enable coalesce mode by default) posted (#2) for review on master by Brian Foster (bfoster)

Comment 2 Anand Avati 2013-08-26 18:11:27 UTC
REVIEW: http://review.gluster.org/5624 (cluster/stripe: enable coalesce mode by default) posted (#3) for review on master by Brian Foster (bfoster)

Comment 3 Anand Avati 2013-08-29 04:33:47 UTC
COMMIT: http://review.gluster.org/5624 committed in master by Anand Avati (avati) 
------
commit bf63e7c6a3fa1bfceb14acf5504b0d52833f7118
Author: Brian Foster <bfoster>
Date:   Wed Aug 14 07:09:52 2013 -0400

    cluster/stripe: enable coalesce mode by default
    
    It has been available for a while now and is probably the sane
    default due to the more efficient layout and performance benefit.
    
    BUG: 1001207
    Change-Id: I6275f9741866c0afd6e685f8dc5867a86485fd20
    Signed-off-by: Brian Foster <bfoster>
    Reviewed-on: http://review.gluster.org/5624
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Anand Avati <avati>

Comment 4 Niels de Vos 2014-04-17 11:46:25 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.5.0, please reopen this bug report.

glusterfs-3.5.0 has been announced on the Gluster Developers mailinglist [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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/6137
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user