TrueCloudLab/restic
16
0
Fork 2
Code Issues 1 Pull requests 1 Projects Releases Packages Wiki Activity Actions 1

Merge pull request #986 from restic/fix-regression-985

Browse source 
Allow many idle connections per host
This commit is contained in:
Alexander Neumann 2017-05-31 20:49:50 +02:00
commit fba6211c99
2 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
CHANGELOG.md
View file

@ -7,6 +7,12 @@ Important Changes in 0.X.Y
Small changes: Small changes:
-------------- --------------
* Backends based on HTTP now allow several idle connections in parallel. This
is especially important for the REST backend, which (when used with a local
server) may create a lot connections and exhaust available ports quickly.
https://github.com/restic/restic/issues/985
https://github.com/restic/restic/pull/986
* Regular status report: We've removed the status report that was printed * Regular status report: We've removed the status report that was printed
every 10 seconds when restic is run non-interactively. You can still force every 10 seconds when restic is run non-interactively. You can still force
reporting the current status by sending a `USR1` signal to the process. reporting the current status by sending a `USR1` signal to the process.

1
src/restic/backend/http_transport.go
View file

@ -18,6 +18,7 @@ func Transport() http.RoundTripper {
DualStack: true, DualStack: true,
}).DialContext, }).DialContext,
MaxIdleConns: 100, MaxIdleConns: 100,
MaxIdleConnsPerHost: 100,
IdleConnTimeout: 90 * time.Second, IdleConnTimeout: 90 * time.Second,
TLSHandshakeTimeout: 10 * time.Second, TLSHandshakeTimeout: 10 * time.Second,
ExpectContinueTimeout: 1 * time.Second, ExpectContinueTimeout: 1 * time.Second,