You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2019/12/17 18:48:46 UTC

[GitHub] [couchdb] davisp commented on issue #2320: conflicting revisions getting created instead of getting "conflict" error response within a node

davisp commented on issue #2320: conflicting revisions getting created instead of getting "conflict" error response within a node
URL: https://github.com/apache/couchdb/issues/2320#issuecomment-566697019
 
 
   This is an effect of quorum writes in a cluster. What happens during a clustered write is that the updates are sent to all nodes in the cluster and the responses are then collected and returned.
   
   In your case what is happening is that you have two concurrent writes that are then distributed to all shard copies. Say you want to write both Rev1 and Rev2 concurrently. Depending on timing, those may arrive at nodes in different orders. I.e., node1 might see Rev1 first, while node2 might see `Rev2` first. In that case both updates will be accepted and the result would then be a conflict written on both nodes.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services