Bug 1428082

Summary:	client: Increase default ping-timeout to 180 seconds
Product:	[Community] GlusterFS	Reporter:	Vijay Bellur <vbellur>
Component:	protocol	Assignee:	bugs <bugs>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	atumball, bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-08 17:20:18 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vijay Bellur 2017-03-01 19:06:23 UTC

client: Increase default ping-timeout to 180 seconds

Summary:
- We've seen lots of issues when the ping timeout is too low @ 60 seconds.
- This diff defaults the value to 180 seconds.
- This is a cherry-pick of D3753765 to 3.8.

Signed-off-by: Shreyas Siravara <sshreyas>

Change-Id: I70b96b027ac024df63af4ca1aa768f973295b7e4
Reviewed-on: http://review.gluster.org/16219
Smoke: Gluster Build System <jenkins.org>
Tested-by: Shreyas Siravara <sshreyas>
CentOS-regression: Gluster Build System <jenkins.org>
NetBSD-regression: NetBSD Build System <jenkins.org>
Reviewed-by: Kevin Vigor <kvigor>

Comment 1 Worker Ant 2017-03-01 20:49:15 UTC

REVIEW: https://review.gluster.org/16813 (client: Increase default ping-timeout to 180 seconds) posted (#1) for review on master by Vijay Bellur (vbellur)

Comment 2 Amar Tumballi 2018-10-08 17:20:18 UTC

We now have 'site.h', which can be used to different default values for different env.

Closing as WONTFIX.