Bug 1158648

Summary:	[FEAT] Make own-thread option configurable separately from SSL
Product:	[Community] GlusterFS	Reporter:	Jeff Darcy <jdarcy>
Component:	transport	Assignee:	Jeff Darcy <jdarcy>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-bugs, vagarwal
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	glusterfs-3.7.0	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-05-14 17:28:14 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 Jeff Darcy 2014-10-29 19:21:45 UTC

Right now there's no way to turn on own-thread separately from SSL, other than with some exceptionally hairy and hard-to-guess --xlator-option escapes.  For those who want the increased parallelism and performance of own-thread without SSL, we should make it separately configurable with little effort.

Comment 1 Anand Avati 2014-10-29 19:23:16 UTC

REVIEW: http://review.gluster.org/8931 (glusterd: add option support for own-thread) posted (#2) for review on master by Jeff Darcy (jdarcy)

Comment 2 Anand Avati 2014-10-31 04:13:35 UTC

COMMIT: http://review.gluster.org/8931 committed in master by Krishnan Parthasarathi (kparthas) 
------
commit 4120e8a47a6d9b8cb3e4bf6f8ede6d26667fb673
Author: Jeff Darcy <jdarcy>
Date:   Tue Oct 14 15:16:24 2014 -0400

    glusterd: add option support for own-thread
    
    Like enabling SSL, enabling own-thread has to be done separately for
    clients and servers.
    
     * client.own-thread for clients (including internal like self-heal)
    
     * server.own-thread for servers (including e.g. glusterd)
    
    It's very unlikely that you would ever want to set one without the
    other, but they're separate anyway just in case.  Check for "private
    polling thread" in the relevant logs to make sure the option took
    effect, because otherwise you might not notice any difference besides
    inreased performance.  ;)
    
    Change-Id: Ifaee8de52f0b959bcdf7f6b56faeee549ee56604
    BUG: 1158648
    Signed-off-by: Jeff Darcy <jdarcy>
    Reviewed-on: http://review.gluster.org/8931
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Shyamsundar Ranganathan <srangana>
    Reviewed-by: Krishnan Parthasarathi <kparthas>
    Tested-by: Krishnan Parthasarathi <kparthas>

Comment 3 Niels de Vos 2015-05-14 17:28:14 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.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 4 Niels de Vos 2015-05-14 17:35:40 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.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 5 Niels de Vos 2015-05-14 17:38:03 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.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 6 Niels de Vos 2015-05-14 17:44:21 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.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user