Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 23 Mar 2011 18:23:05 +0000 (UTC)
From: "Erik Onnen (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <1420123325.6752.1300904585745.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2083116216.6564.1300900685967.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-3692) Handle RejectedExecutionException
 in HTable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010277#comment-13010277 ] 

Erik Onnen commented on HBASE-3692:
-----------------------------------

Not sure that would be always correct. The pool has a finite number of tasks it can accept and if the back end servers are overloaded it's possible that you falsely blame incorrect code when in reality you're overwhelming the region servers.

> Handle RejectedExecutionException in HTable
> -------------------------------------------
>
>                 Key: HBASE-3692
>                 URL: https://issues.apache.org/jira/browse/HBASE-3692
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.90.1
>            Reporter: Jean-Daniel Cryans
>             Fix For: 0.92.0
>
>
> A user on IRC yesterday had an issue with RejectedExecutionException coming out of HTable sometimes. Apart from being very confusing to the user as it comes with no message at all, it exposes the HTable internals. 
> I think we should handle it and instead throw something like DontUseHTableInMultipleThreadsException or something more clever. In his case, the user had a HTable leak with the pool that he was able to figure out once I told him what to look for.
> It could be an unchecked exception and we could consider adding in 0.90 but marking for 0.92 at the moment.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira