[
https://issues.apache.org/jira/browse/COUCHDB-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083791#comment-13083791
]
Paul Joseph Davis commented on COUCHDB-1246:
--------------------------------------------
I've got it so that I can reproduce the fact that couchjs processes aren't
going away. I'm not able to get it so that it hits the timeout though. It ends
up getting to one under than then sits there. So I'm either not reproducing
this directly, or perhaps other people have concurrency adding to the issue.
Anyway, I'll keep trying to track down where we lose processes.
> CouchJS process spawned and not killed on each Reduce Overflow Error
> --------------------------------------------------------------------
>
> Key: COUCHDB-1246
> URL: https://issues.apache.org/jira/browse/COUCHDB-1246
> Project: CouchDB
> Issue Type: Bug
> Components: JavaScript View Server
> Affects Versions: 1.1
> Environment: Linux Debian Squeeze
> [query_server_config]
> reduce_limit = true
> os_process_limit = 25
> Reporter: Michael Newman
> Attachments: categories
>
>
> Running the view attached results in a reduce_overflow_error. For each
> reduce_overflow_error a process of /usr/lib/couchdb/bin/couchjs
> /usr/share/couchdb/server/main.js starts running. Once this gets to 25, which
> is the os_process_limit by default, all views result in a server error:
> timeout {gen_server,call,[couch_query_servers,{get_proc,<<"javascript">>}]}
> As far as I can tell, these processes and the non-response from the views
> will continue until couch is restarted.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
