nickva opened a new pull request, #5337:
URL: https://github.com/apache/couchdb/pull/5337
Previously, when mem3 failed such that it's shards ets table disappeared,
while the replicator was processing doc updates, it was possible for the
`couch_replicator_utils:owner/2` to raise `error:badarg` (passed through from
the ets:* calls) to be registered as a malformed (failed) replicator doc
update. After that, the replication job would be effectively stuck in the
`failed` state until the user took action to re-create it.
To fix it, change the doc update callback to on only fail jobs on explicit
replication doc parse failures (they have `throw({the bad_rep_doc, _})
exception pattern). In any other case let the exception crash the db changes
feed and let the supervisor restart it.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@couchdb.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
