Bug 1404181

Summary:	[Ganesha+SSL] : Ganesha crashes on all nodes on volume restarts
Product:	[Community] GlusterFS	Reporter:	rjoseph
Component:	libgfapi	Assignee:	rjoseph
Status:	CLOSED CURRENTRELEASE	QA Contact:	Sudhir D <sdharane>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	amukherj, asoman, bturner, bugs, jthottan, pgurusid, rhinduja, rhs-bugs, rjoseph, skoduri, storage-qa-internal, vdas
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.10.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1398798	Environment:
Last Closed:	2017-03-06 17:39:10 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:
Bug Depends On:	1398798
Bug Blocks:

Comment 1 Worker Ant 2016-12-15 12:44:34 UTC

REVIEW: http://review.gluster.org/16141 (socket: socket disconnect should wait for poller thread exit) posted (#1) for review on master by Rajesh Joseph (rjoseph)

Comment 2 Worker Ant 2016-12-15 12:48:09 UTC

REVIEW: http://review.gluster.org/16141 (socket: socket disconnect should wait for poller thread exit) posted (#2) for review on master by Rajesh Joseph (rjoseph)

Comment 3 Worker Ant 2016-12-15 14:10:33 UTC

REVIEW: http://review.gluster.org/16141 (socket: socket disconnect should wait for poller thread exit) posted (#3) for review on master by Rajesh Joseph (rjoseph)

Comment 4 Worker Ant 2016-12-22 04:49:23 UTC

COMMIT: http://review.gluster.org/16141 committed in master by Raghavendra G (rgowdapp) 
------
commit af6769675acbbfd780fa2ece8587502d6d579372
Author: Rajesh Joseph <rjoseph>
Date:   Tue Dec 13 15:28:42 2016 +0530

    socket: socket disconnect should wait for poller thread exit
    
    When SSL is enabled or if "transport.socket.own-thread" option is set
    then socket_poller is run as different thread. Currently during
    disconnect or PARENT_DOWN scenario we don't wait for this thread
    to terminate. PARENT_DOWN will disconnect the socket layer and
    cleanup resources used by socket_poller.
    
    Therefore before disconnect we should wait for poller thread to exit.
    
    Change-Id: I71f984b47d260ffd979102f180a99a0bed29f0d6
    BUG: 1404181
    Signed-off-by: Rajesh Joseph <rjoseph>
    Reviewed-on: http://review.gluster.org/16141
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Kaushal M <kaushal>
    Reviewed-by: Raghavendra Talur <rtalur>
    Reviewed-by: Raghavendra G <rgowdapp>

Comment 5 Shyamsundar 2017-03-06 17:39:10 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/