couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Hammond (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 22:35:14 GMT

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

Mark Hammond commented on COUCHDB-370:
--------------------------------------

If I understand correctly, couchspawnkillable will terminate couch's children when couch explicitly
asks, but should couch go away silently and suddenly these children may continue to exist.
 While couch stopping would *usually* kill the child due to the child's stdin being closed,
this would not be the case if the child process was in an infinite loop and didn't get back
to trying to read stdin.

> 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