You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Paul Joseph Davis (Commented) (JIRA)" <ji...@apache.org> on 2011/10/14 00:42:13 UTC

[jira] [Commented] (COUCHDB-1305) keep db crashes from bubbling through couch_server when possible

    [ https://issues.apache.org/jira/browse/COUCHDB-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13127064#comment-13127064 ] 

Paul Joseph Davis commented on COUCHDB-1305:
--------------------------------------------

Sounds like a good idea to me.
                
> keep db crashes from bubbling through couch_server when possible
> ----------------------------------------------------------------
>
>                 Key: COUCHDB-1305
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1305
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Database Core
>            Reporter: Randall Leeds
>            Assignee: Randall Leeds
>            Priority: Minor
>             Fix For: 1.3
>
>
> COUCHDB-1050 shows how an error in a db process can cause unexpected 'EXIT' messages to reach couch_server. These messages cause couch_server to restart, forcing all open databases to close, which has nasty effects like killing replications and index generation in unrelated databases. I suggest we use the couch_dbs_by_pid table to swallow the error, cleanup the ETS tables, log a message and continue. If a match isn't found in the table then the current unexpected message crash should be preserved.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira