You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Elliott Clark (JIRA)" <ji...@apache.org> on 2013/09/20 23:39:00 UTC
[jira] [Resolved] (HBASE-9587) AsyncProcess max outstanding cap
should be per connection
[ https://issues.apache.org/jira/browse/HBASE-9587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliott Clark resolved HBASE-9587.
----------------------------------
Resolution: Won't Fix
Looks like were going a different route to cap this.
> AsyncProcess max outstanding cap should be per connection
> ---------------------------------------------------------
>
> Key: HBASE-9587
> URL: https://issues.apache.org/jira/browse/HBASE-9587
> Project: HBase
> Issue Type: Bug
> Reporter: Elliott Clark
> Assignee: Elliott Clark
>
> JD noticed that when running PE there were ~4k threads running. This is waaaaay too many.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira