couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Kocoloski (JIRA)" <j...@apache.org>
Subject [jira] Closed: (COUCHDB-449) Turn off delayed commits by default
Date Sat, 15 Aug 2009 02:04:14 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Adam Kocoloski closed COUCHDB-449.
----------------------------------

    Resolution: Fixed
      Assignee: Adam Kocoloski

we can always add new issues if folks require finer-grained config options like per-DB defaults
or custom delays.

> 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
>            Assignee: Adam Kocoloski
>            Priority: Blocker
>             Fix For: 0.10
>
>         Attachments: delayed_commits_v1.patch
>
>
> 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.


Mime
View raw message