Github user davisp commented on the pull request:
https://github.com/apache/couchdb-couch-replicator/pull/38#issuecomment-221649847
I didn't see that. Also I'm not sure what a 429 response might include. I
was thinking slightly more fancy in that if you get a 429 you notify the rate
limiter process and it does fancy heuristic type things to its limits. The idea
here is that you're trying to feel out what the limit might be.
Remember that those sorts of limits may or may not be global. So for
instance, one rate limiting proxy might have limits shared between all clients
in which case your 429 rate limiting responder has to feel out how many other
clients are also working which affects what proportion of the rates it could
use.
Also alternatively you could have rates that change during replication so
you'd also want to heuristically try and increase occasionally too (unless set
by a human) so that you aren't replicating slower than need be just because
there was a spike in usage.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
