Bug 912053 - Remove suggested initial values for connection and node timeouts
Summary: Remove suggested initial values for connection and node timeouts
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: GlusterFS
Classification: Community
Component: object-storage
Version: 3.3.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Thiago da Silva
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-17 13:41 UTC by Peter Portante
Modified: 2014-12-14 19:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-12-14 19:40:30 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.