Schedule replication by remote, not by project
We now create a thread pool for each [remote] block found inside of
replication.config. All URLs within that remote block share the same
pool of worker threads. By defining different remote blocks for each
URL the administrator is able to isolate slow WAN links from faster
local warm-spares, ensuring that the more local systems are able to
stay current, even if the WAN gets really far behind.
Bug: GERRIT-200
Signed-off-by: Shawn O. Pearce <sop@google.com>
4 files changed