[
https://issues.apache.org/jira/browse/COUCHDB-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738340#action_12738340
]
Adam Kocoloski commented on COUCHDB-370:
----------------------------------------
Hi Mark, my take on the code in couch_os_process is that if the
couch_os_process gen_server dies for any reason, another process which has been
monitoring that gen_server swoops in and executes a kill -9 on the OS process.
This approach doesn't rely on stdin being read by the child proc.
I could see a sudden Erlang VM death leading to an OS process being orphaned.
If that's happening I think we should focus our efforts on preventing the VM
death :-), but if it's simple to do then having couchspawnkillable monitor the
VM is also a good idea.
> 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.
