[
https://issues.apache.org/jira/browse/COUCHDB-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Shorin closed COUCHDB-2823.
-------------------------------------
Resolution: Not A Problem
That's not a problem.
Update handlers doesn't guarantee conflict-free updates - they are just allows
to apply custom user logic before try to update a document.
With high updates handler request rate from single process you may eventually
cause concurrent updates, because CouchDB will try to run update function on
free query server processes, while others are busy by processing your previous
calls.
That's said, if single document will get updated by multiple times in this
situation, CouchDB will raise update conflict for one of the attempt.
Conflicts are not an error, it's a marker that helps you to detect side changes
and take them into account without losing any bit of data. Don't fear them -
use them!
> CouchDB sometimes returns: 409 {"error":"conflict...
> -----------------------------------------------------
>
> Key: COUCHDB-2823
> URL: https://issues.apache.org/jira/browse/COUCHDB-2823
> Project: CouchDB
> Issue Type: Bug
> Security Level: public(Regular issues)
> Reporter: ASF subversion and git services
>
> CouchDB sometimes returns:
> 409 {"error":"conflict","reason":"Document update conflict."}
> when I use a update handle defined in a design document even if there is no
> conflict and the document have been updated.
> I've only noticed this when I send a lot of update request quickly in
> succession.
> *Reporter*: Petter Lundahl
> *E-mail*: [mailto:[email protected]]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
