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

["Jeff Whiting (JIRA)" <ji...@apache.org>]

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

Jeff Whiting commented on HBASE-3692:
-------------------------------------

We have seen the same stack trace and have had the same problem.  Seems useful to know that others are having this problem as well.  The exception is confusing, and I don't really understand what is going on...

java.util.concurrent.RejectedExecutionException
 at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:1956)
 at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:816)
 at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1337)
 at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:120)
 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 are running cdh3u0.

We do implement our own connection pooling on top of the HTablePool while we always put it back to our connection pool stuff is rarely put back into the HTablePool, would that cause this problem?

> 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
>
> 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