You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Chinmay Dhodapkar (Commented) (JIRA)" <ji...@apache.org> on 2012/03/14 20:10:45 UTC

[jira] [Commented] (HBASE-3692) Handle RejectedExecutionException in HTable

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

Chinmay Dhodapkar commented on HBASE-3692:
------------------------------------------

@anyone

We using  CDH3u0 dist and we see the same issue. It occurs during htable.put. Increasing the pool size seems to delay the issue (or just reduce the probability) . [HTablePool(conf, 100)  vs HTablePool(conf, Interger.MAX_VALUE)]

As per CDH support, HBASE-3777 along with the thread management changes in HBASE-3553 might have solved this issue....but I seriously doubt it. Just wanted to check if anybody tried CDH3u3 before i embark onto a wild goose chase...

Thanks.
                
> 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
>         Attachments: test_datanucleus.zip
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira