Handle 429

When we encounter a 429, we retry with a different set of retries and
timeout. This will theoretically reduce client replication overload.
When 429s have stopped, it's possible that a 500 error could occur.
Then the retry mechanism should go back to the original way for
backwards compatibility.

BugzId:60007
COUCHDB-3010
2 files changed
tree: 2b08f4964e9274e3ea847d397c6d362e6ec6fa3c
  1. priv/
  2. src/
  3. test/
  4. .gitignore
  5. .travis.yml
  6. LICENSE