zrepl/util
Christian Schwarz 000d8bba66 hotfix: limit concurrency of zfs send & recv commands
ATM, the replication logic sends all dry-run requests in parallel,
which might overwhelm the ZFS pool on the sending side.
Since we use rpc/dataconn for dry sends, this also opens one TCP
connection per dry-run request.

Use a sempahore to limit the degree of concurrency where we know it is a
problem ATM.
As indicated by the comments, the cleaner solution would involve some
kind of 'resource exhaustion' error code.

refs #161
refs #164
2019-03-28 22:17:12 +01:00
..
bytecounter run golangci-lint and apply suggested fixes 2019-03-27 13:12:26 +01:00
chainedio run golangci-lint and apply suggested fixes 2019-03-27 13:12:26 +01:00
chainlock format source tree using goimports 2019-03-22 19:41:12 +01:00
chunking run golangci-lint and apply suggested fixes 2019-03-27 13:12:26 +01:00
connlogger run golangci-lint and apply suggested fixes 2019-03-27 13:12:26 +01:00
devnoop rpc/dataconn: microbenchmark 2019-03-13 13:57:21 +01:00
envconst replication/driver: automatic retries on connectivity-related errors 2019-03-13 15:00:40 +01:00
iocommand run golangci-lint and apply suggested fixes 2019-03-27 13:12:26 +01:00
optionaldeadline run golangci-lint and apply suggested fixes 2019-03-27 13:12:26 +01:00
semaphore hotfix: limit concurrency of zfs send & recv commands 2019-03-28 22:17:12 +01:00
socketpair socketpair: directly export *net.UnixConn (and add test for that behavior) 2019-03-13 11:36:34 +01:00