[jira] [Commented] (COUCHDB-1246) CouchJS process spawned and not killed on each Reduce Overflow Error
[
https://issues.apache.org/jira/browse/COUCHDB-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086826#comment-13086826
]
Filipe Manana commented on COUCHDB-1246:
Thanks Paul, looks good to me.
> 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: COUCHDB-1246.patch, categories, os_pool_trunk.patch,
> os_pool_trunk.patch, os_pool_trunk.patch
>
>
> 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
[jira] [Commented] (COUCHDB-1246) CouchJS process spawned and not killed on each Reduce Overflow Error
[
https://issues.apache.org/jira/browse/COUCHDB-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086769#comment-13086769
]
Paul Joseph Davis commented on COUCHDB-1246:
I swear to christ I clicked the for contribution button. Not that it matters.
Also, how does one delete attachments?
> 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: COUCHDB-1246.patch, COUCHDB-1246.patch, categories,
> os_pool_trunk.patch, os_pool_trunk.patch, os_pool_trunk.patch
>
>
> 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
[jira] [Commented] (COUCHDB-1246) CouchJS process spawned and not killed on each Reduce Overflow Error
[
https://issues.apache.org/jira/browse/COUCHDB-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086083#comment-13086083
]
Paul Joseph Davis commented on COUCHDB-1246:
Filipe,
Awesome work on the test. When I stared at it last I was contemplating writing
a huge monolithic thing to setup a view and do all that crazy stuff. Knowing we
can work down at the os process level should allow us to get a better handle on
this.
I'll try looking at this closer tonight or tomorrow.
> 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: COUCHDB-1246.patch, categories, os_pool_trunk.patch
>
>
> 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
[jira] [Commented] (COUCHDB-1246) CouchJS process spawned and not killed on each Reduce Overflow Error
[
https://issues.apache.org/jira/browse/COUCHDB-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083873#comment-13083873
]
Michael Newman commented on COUCHDB-1246:
-
Interesting. I run this view 25 times and I get 25 couchjs processes and any
other view I request after that returns this timeout.
This is a Debian server running on an Amazon EC2 micro instance if that helps
at all.
> 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
[jira] [Commented] (COUCHDB-1246) CouchJS process spawned and not killed on each Reduce Overflow Error
[
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
[jira] [Commented] (COUCHDB-1246) CouchJS process spawned and not killed on each Reduce Overflow Error
[
https://issues.apache.org/jira/browse/COUCHDB-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083557#comment-13083557
]
Michael Newman commented on COUCHDB-1246:
-
Each reduce_overflow_error, yes. This does not happen with another (proper)
view.
> 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
[jira] [Commented] (COUCHDB-1246) CouchJS process spawned and not killed on each Reduce Overflow Error
[
https://issues.apache.org/jira/browse/COUCHDB-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083545#comment-13083545
]
Paul Joseph Davis commented on COUCHDB-1246:
And each call to the view ends up creating a new couchjs process right?
> 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
