forked from TrueCloudLab/frostfs-http-gw
[#146] Update default values for HTTP_GW_READ/WRITE_TIMEOUT
10 minute upload and 5 minute download timeouts are long enough to handle average size objects in the real networks. For big data streams these timeouts should be disabled. Signed-off-by: Alex Vanin <alexey@nspcc.ru>
This commit is contained in:
parent
4f2b21a14b
commit
d906732ef4
4 changed files with 11 additions and 6 deletions
|
@ -125,6 +125,11 @@ You can tune HTTP read and write buffer sizes as well as timeouts with
|
|||
`HTTP_GW_WEB_WRITE_BUFFER_SIZE` and `HTTP_GW_WEB_WRITE_TIMEOUT` environment
|
||||
variables.
|
||||
|
||||
**Note:** to allow upload and download of big data streams, disable read
|
||||
and write timeouts correspondingly. To do that, set `HTTP_GW_WEB_READ_TIMEOUT=0`
|
||||
and `HTTP_GW_WEB_WRITE_TIMEOUT=0`. Otherwise, HTTP Gateway will terminate
|
||||
request with data stream after timeout.
|
||||
|
||||
`HTTP_GW_WEB_STREAM_REQUEST_BODY` environment variable can be used to disable
|
||||
request body streaming (effectively it'll make gateway accept file completely
|
||||
first and only then try sending it to NeoFS).
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue