nickva opened a new issue, #6029: URL: https://github.com/apache/couchdb/issues/6029
### Version unknown ### Describe the problem you're encountering When we enabled serialize_worker_startup=true on a cluster we noticed user could not update their _replicator docs. Replication would finish, replicator updated the `completed` state. User grabs the rev (say 2-y) and then tries to use the rev and it gets the 409. Retrying to get the revs doesn't make any difference: user still gets the same rev (2-y) and still gets a 409s when trying to use it. There is not 3-z rev to wait on, 2-y is the latest rev. Eventually when the internal replicator catches up, the user can finally make progress and update the doc (use 2-y to delete it) ### Expected Behaviour User can grab the latest rev then use the latest revs to update the docs in the db ### Steps to Reproduce _No response_ ### Your Environment _No response_ ### Additional Context _No response_ -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
