alvarolivie opened a new issue, #6175: URL: https://github.com/apache/couchdb/issues/6175
### Version 3.4.2 ### Describe the problem you're encountering We run a cluster with 3 nodes and 2 needed for write quorum. When updating a document that has an attachment stub just been written we sometimes get `412` and error `missing_stub`. When we check again the write has gone through with all revisions on all copies and no conflicts. This happens when the update is sent right after the document was created and one copy has not committed the first revision yet. That copy's `update_docs` throws `missing_stub`. `handle_message` then throws on that single worker's reply instead of counting it toward the quorum. The other two copies have already applied the update. ### Expected Behaviour The error `missing_stub` should count towards the quorum the same way `conflict` does and behave the same way. ### Steps to Reproduce I managed to recreate this localy with a cluster using image `couchdb:3.5.3` with a table with config n=3, w=2 and slowing one node slowed down with `docker update --cpus 0.05 couch3`. Then create an entry with an attachment and immediately update it. I did this for 200 documents and managed to get the error 15 times. ### Your Environment Seen in `couchdb:3.4.3` in production with settings q=2, n=3, w=2, r=2. (Running in a Kubernetes StatefulSet) Recreated in a similar environment using the newest image 3.5.3 ### Additional Context This was originally opened in [issue 584](https://github.com/apache/couchdb/issues/584) but nobody answered. Let me know if you want me to continue there. Also happy to prep a PR if needed. -- 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]
