Reduce likelihood of a bad replication job taking down the job supervisor

While we can't disable max_restart_intensity, we can make it unlikely
to happen. Ordinarily, we would want this behaviour, but replication
jobs involve human input. A bad password, or malformed url, etc, can
cause repeated and fast crashing.

For now, we require ten crashes within one second before we would
bounce the job supervisor. In future, we should manage replication
jobs with greater care.

COUCHDB-2975
1 file changed
tree: dbe220ab1814bb23ea0e95ae8e91e6bca3bdadc3
  1. priv/
  2. src/
  3. test/
  4. .gitignore
  5. .travis.yml
  6. LICENSE