Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Fri, 20 Sep 2013 21:39:00 +0000 (UTC)
From: "Elliott Clark (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12669538.1379622089068.171115.1379713140836@arcas>
In-Reply-To: <JIRA.12669538.1379622089068@arcas>
References: <JIRA.12669538.1379622089068@arcas>
Subject: [jira] [Resolved] (HBASE-9587) AsyncProcess max outstanding cap
 should be per connection
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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