kocolosk commented on issue #3939: URL: https://github.com/apache/couchdb/issues/3939#issuecomment-1048949348
Oh, and as to the consistency violation -- I strongly suspect we're immune, because the ultimate source of truth for whether the update is committed is in the normal `couch_db_updater` logic, where we've run all manner of tests stressing the correctness of the system under concurrent load. We could have plenty of cases where `C1` and `C2` are both writing attachment data to disk concurrently, but in the end the revision tree for a particular shard copy will only commit the update from one of them in interactive mode. -- 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]
