Github user nickva commented on the issue:
https://github.com/apache/couchdb-fabric/pull/86
A 5xx error seems more appropriate it seems as this implies something has
gone wrong on the server. The other question could be what should we do in the
replicator. Should we keep trying in the open_revs request or exit and crash
the whole job?
Most errors at that point will result in retries with backoff until it
crashes with a `kaboom` exit. Then it will restart the whole replication job (
which starts a new change feed etc) and it repeats again.
If 3rd node was down temporarily and comes back then retries will work ok.
But what if it doesn't? Does the change feed crash or just skips the
document... I am entirely sure.
---
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.
---
