[
https://issues.apache.org/jira/browse/COUCHDB-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740093#action_12740093
]
Adam Kocoloski commented on COUCHDB-449:
----------------------------------------
+1 on turning off delayed commits by default
+1 for enabling them on a per-DB basis
+0 for making the threshold configurable
We should add a DB-level configuration facility at some point. It'd be nice to
be able to edit this setting (and others, like continuous replication) without
server-level admin privileges.
> Turn off delayed commits by default
> -----------------------------------
>
> Key: COUCHDB-449
> URL: https://issues.apache.org/jira/browse/COUCHDB-449
> Project: CouchDB
> Issue Type: Bug
> Components: Database Core
> Affects Versions: 0.9, 0.9.1
> Reporter: Jan Lehnardt
> Priority: Blocker
> Fix For: 0.10
>
>
> Delayed commits make CouchDB significantly faster. They also open a one
> second window for data loss. In 0.9 and trunk, delayed commits are enabled by
> default and can be overridden with HTTP headers and an explicit API call to
> flush the write buffer. I suggest to turn off delayed commits by default and
> use the same overrides to enable it per request. A per-database option is
> possible, too.
> One concern is developer workflow speed. The setting affects the test suite
> performance significantly. I'd opt to change couch.js to set the appropriate
> header to enable delayed commits for tests.
> CouchDB should guarantee data safety first and speed second, with sensible
> overrides.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
