openstack/swift
Code Issues Proposed changes

Add concurrent_gets to proxy.conf man page

Browse Source 
Change-Id: Iab1beff4899d096936c0e5915f3ec32364b3e517
Closes-Bug: #1559347
This commit is contained in:
Alistair Coles 2017-09-27 14:11:14 +01:00
parent ff23dcdf3a
commit 5c76b9e691
2 changed files with 11 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/manpages/proxy-server.conf.5
View File

@ -1023,6 +1023,15 @@ The valid values for sorting_method are "affinity", "shuffle", and "timing".
.IP \fBtiming_expiry\fR
If the "timing" sorting_method is used, the timings will only be valid for
the number of seconds configured by timing_expiry. The default is 300.
.IP \fBconcurrent_gets\fR
If "on" then use replica count number of threads concurrently during a GET/HEAD
and return with the first successful response. In the EC case, this parameter
only affects an EC HEAD as an EC GET behaves differently. Default is "off".
.IP \fBconcurrency_timeout\fR
This parameter controls how long to wait before firing off the next
concurrent_get thread. A value of 0 would we fully concurrent, any other number
will stagger the firing of the threads. This number should be between 0 and
node_timeout. The default is the value of conn_timeout (0.5).
.IP \fBrequest_node_count\fR
Set to the number of nodes to contact for a normal request. You can use '* replicas'
at the end to have it use the number given times the number of

4
doc/source/deployment_guide.rst
View File

@ -1943,12 +1943,12 @@ concurrent_gets off Use replica count numbe
GET/HEAD and return with the
first successful response. In
the EC case, this parameter only
effects an EC HEAD as an EC GET
affects an EC HEAD as an EC GET
behaves differently.
concurrency_timeout conn_timeout This parameter controls how long
to wait before firing off the
next concurrent_get thread. A
value of 0 would we fully concurrent
value of 0 would we fully concurrent,
any other number will stagger the
firing of the threads. This number
should be between 0 and node_timeout.