Bug 1452038

Summary:	gluster fuse client losing connection to gluster volume frequently
Product:	[Community] GlusterFS	Reporter:	Milind Changire <mchangir>
Component:	rpc	Assignee:	Milind Changire <mchangir>
Status:	CLOSED EOL	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	3.10	CC:	ahatfiel, amukherj, bkunal, bugs, csaba, knakai, mchangir, moagrawa, nbalacha, nchilaka, pdhange, rcyriac, rgowdapp, rhinduja, rhs-bugs, storage-qa-internal
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1426059	Environment:
Last Closed:	2018-06-20 18:26:51 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:	1426059
Bug Blocks:

Comment 1 Worker Ant 2017-05-18 09:32:44 UTC

REVIEW: https://review.gluster.org/17330 (rpc: add options to manage socket keepalive lifespan) posted (#1) for review on release-3.10 by Milind Changire (mchangir)

Comment 2 Worker Ant 2017-05-18 12:21:00 UTC

REVIEW: https://review.gluster.org/17330 (rpc: add options to manage socket keepalive lifespan) posted (#2) for review on release-3.10 by Milind Changire (mchangir)

Comment 3 Milind Changire 2017-05-18 17:21:36 UTC

Description of problem:
The application using gluster fuse mount crashed on 2 occasions due to gluster fuse (mount point) disconnected from gluster volume. Also, it is also observed that the bricks processes are also disconnecting from each other at same time when client seeing disconnect from gluster volume. The primary investigation shows the problem in customer network configuration.

Comment 4 Worker Ant 2017-06-02 03:52:13 UTC

REVIEW: https://review.gluster.org/17330 (rpc: add options to manage socket keepalive lifespan) posted (#3) for review on release-3.10 by Milind Changire (mchangir)

Comment 5 Worker Ant 2017-06-06 07:13:26 UTC

REVIEW: https://review.gluster.org/17330 (rpc: add options to manage socket keepalive lifespan) posted (#4) for review on release-3.10 by Milind Changire (mchangir)

Comment 6 Worker Ant 2017-06-20 04:58:29 UTC

COMMIT: https://review.gluster.org/17330 committed in release-3.10 by Raghavendra Talur (rtalur) 
------
commit cf1f33a261b093a5cdb17406f3bc8e301caf9581
Author: Milind Changire <mchangir>
Date:   Tue Jun 6 12:42:40 2017 +0530

    rpc: add options to manage socket keepalive lifespan
    
    Problem:
    Default values for handling socket timeouts for brick responses are
    insufficient for aggressive applications such as databases.
    
    Solution:
    Add 1:1 gluster options for keepalive, keepalive-idle,
    keepalive-interval and keepalive-timeout as per the socket level options
    available as per tcp(7) man page.
    
    Default values for options are NOT agressive and continue to be values
    which result in default timeout when only the keep alive option is
    turned on.
    
    These options are Linux specific and will not be applicable to the
    *BSDs.
    
    mainline:
    > BUG: 1426059
    > Signed-off-by: Milind Changire <mchangir>
    > Reviewed-on: https://review.gluster.org/16731
    > Smoke: Gluster Build System <jenkins.org>
    > CentOS-regression: Gluster Build System <jenkins.org>
    > NetBSD-regression: NetBSD Build System <jenkins.org>
    > Reviewed-by: Raghavendra G <rgowdapp>
    (cherry picked from commit 6b8df081b46ac4f485c86a5052fc30472e74bfbb)
    
    Change-Id: I2a08ecd949ca8ceb3e090d336ad634341e2dbf14
    BUG: 1452038
    Signed-off-by: Milind Changire <mchangir>
    Reviewed-on: https://review.gluster.org/17330
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Raghavendra Talur <rtalur>

Comment 7 Shyamsundar 2018-06-20 18:26:51 UTC

This bug reported is against a version of Gluster that is no longer maintained (or has been EOL'd). See https://www.gluster.org/release-schedule/ for the versions currently maintained.

As a result this bug is being closed.

If the bug persists on a maintained version of gluster or against the mainline gluster repository, request that it be reopened and the Version field be marked appropriately.