Bug 912053

Summary: Remove suggested initial values for connection and node timeouts
Product: [Community] GlusterFS Reporter: Peter Portante <pportant>
Component: object-storageAssignee: Thiago da Silva <thiago>
Status: CLOSED DEFERRED QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: bugs, gluster-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-14 19:40:30 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 Peter Portante 2013-02-17 13:41:00 UTC
The reason for suggested node and connection timeouts for account, container and object servers is not documented correctly, and the values themselves are too high.

The default values for node and connection timeouts maintained by Swift should be sufficient for almost all gluster/swift installations.

Comment 2 Niels de Vos 2014-11-27 14:54:11 UTC
The version that this bug has been reported against, does not get any updates from the Gluster Community anymore. Please verify if this report is still valid against a current (3.4, 3.5 or 3.6) release and update the version, or close this bug.

If there has been no update before 9 December 2014, this bug will get automatocally closed.