hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Onnen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3692) Handle RejectedExecutionException in HTable
Date Tue, 29 Mar 2011 19:56:05 GMT

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

Erik Onnen commented on HBASE-3692:

Oops. Stack trace was:

Caused by: java.util.concurrent.RejectedExecutionException
        at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:1768)
        at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:767)
        at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:658)
        at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:92)
        at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatch(HConnectionManager.java:1136)
        at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchOfPuts(HConnectionManager.java:1234)
        at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:819)
        at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:675)
        at org.apache.hadoop.hbase.client.HTable.put(HTable.java:660)

We also run with a configuration of hbase.htable.threads.max=128. Despite attempting that
configuration and using nearly identical code, I still can't manage to reproduce the exception.

> 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

View raw message