incubator-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] Commented: (COUCHDB-370) If the CouchDB vm is dies or is killed, view subprocesses (js) are not automatically killed
Date Sun, 02 Aug 2009 13:29:14 GMT

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

Adam Kocoloski commented on COUCHDB-370:
----------------------------------------

Hi Mark, I think couchspawnkillable was supposed the solution to this ticket.

> If the CouchDB vm is dies or is killed, view subprocesses (js) are not automatically
killed
> -------------------------------------------------------------------------------------------
>
>                 Key: COUCHDB-370
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-370
>             Project: CouchDB
>          Issue Type: Bug
>          Components: JavaScript View Server
>    Affects Versions: 0.9
>            Reporter: Damien Katz
>            Priority: Minor
>
> If CouchDB dies or is killed, it's subprocess are not forcefully killed. If the subprocesses
are in infinite loops, they will never die. We need some kind of external watchdog process,
or processes that kill the subprocess automatically if the CouchDB erlang vm dies.

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