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
..
driver	run golangci-lint and apply suggested fixes	2019-03-27 13:12:26 +01:00
logic	hotfix: limit concurrency of zfs send & recv commands	2019-03-28 22:17:12 +01:00
report	replication/driver: automatic retries on connectivity-related errors	2019-03-13 15:00:40 +01:00
replication.go	replication: refactor driving logic (no more explicit state machine)	2019-03-13 15:00:40 +01:00