[
https://issues.apache.org/jira/browse/COUCHDB-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738677#action_12738677
]
Mark Hammond commented on COUCHDB-370:
--------------------------------------
Damien writes:
> A correct solution is one or more watchdog processes that watch the
> VM and the subprocess, and if the VM dies, it kills all the subprocesses and
> then itself.
Exactly. I was proposing couch_spawn_killable could serve the role of that
watchdog - it can watch for its parent terminating, then terminate its child
and then itself. Although this isn't a *single* watchdog, it should have the
same end result.
> 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.
