couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Damien Katz (JIRA)" <j...@apache.org>
Subject [jira] Updated: (COUCHDB-334) With deferred commits and 100+ active dbs, CouchDB can lose uncommitted changes
Date Mon, 27 Apr 2009 22:00:31 GMT

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

Damien Katz updated COUCHDB-334:
--------------------------------

    Fix Version/s:     (was: 0.10)
                   0.9.1

> With deferred commits and 100+ active dbs, CouchDB can lose uncommitted changes
> -------------------------------------------------------------------------------
>
>                 Key: COUCHDB-334
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-334
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core
>    Affects Versions: 0.9
>            Reporter: Damien Katz
>            Assignee: Damien Katz
>             Fix For: 0.9.1
>
>
> By default, CouchDB keeps a maximum of 100 databases open and active. This is controlled
by the ini setting max_dbs_open in [couchdb] .
> This limit controls the number of Erlang server processes that are readily available
and hold resources, like file handles, and hold state for deferred commits. Once CouchDB hits
the open database limit, it will always close an idle database and files before opening a
new database file. The problem is that CouchDB would consider instances to be idle even if
they still had deferred commits pending. It would then close the instance and drop it's deferred
commits.

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