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 19:25:55 UTC

[GitHub] [couchdb] davisp commented on issue #2303: fabric doc_update_errors

davisp commented on issue #2303: fabric doc_update_errors
URL: https://github.com/apache/couchdb/issues/2303#issuecomment-566711594
 
 
   Hiya,
   
   As long as you're paying attention to the HTTP status codes that CouchDB is sending you, you'll not lose any document updates. All that this metric is counting is when you've not gotten a quorum write for some identical reason across all replica responses.
   
   For instance, you would see these errors if you attempted to update a document and it returned a `409 Conflict` response. You might also get them if a couple of your nodes are under load and not managing to keep internal replication up to date faster than your write load. In this case you would be seeing `202 Accepted` HTTP status codes indicating that a document was accepted by at least one node but not with an entire quorum. This means the document has been fsync'ed to disk and internal replication will eventually ensure that all `N` copies exist in the cluster.

----------------------------------------------------------------
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