nickva commented on issue #4508: URL: https://github.com/apache/couchdb/issues/4508#issuecomment-1842259307
That might work, but the issue with returning other than a 200 would be strange for a GET request. You could try writting with a `w=3` consistency, though even then if a node disconnects it will be automatically downgraded to `w=2` or `w=1` and you'll get a 202 response. If you read with `r=3` and read all the doc revisions `.../doc'?open_revs=all&latest=true'` (you might have to use `Accept: application/json` request header too) then in the coordinator there is a revision tree built using all the response from all the 3 copies and you should get the latest winning revision that way. Of course if a nodes doesn't respond, we'll automatically downgrade the response automatically to whichever nodes respond only. If you're worried about nodes being out of sync, we've recently sped up the internal replicator, which should help with it. But that's not in a release yet. You could build from source `main` or configure/apply some of the settings in this commit https://github.com/apache/couchdb/commit/85e1fa7913b5a564c1731ad86fbba294a9d9a16c -- 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]
