You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Vladimir Rodionov (Commented) (JIRA)" <ji...@apache.org> on 2011/11/22 02:06:40 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=13154789#comment-13154789 ] 

Vladimir Rodionov commented on HBASE-3692:
------------------------------------------

No, we just hit this issue in one of our reducers (which is single thread by design)
{code}
ava.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:1155)
	at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchOfPuts(HConnectionManager.java:1253)
	at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:836)
	at com.carrieriq.m2m.platform.mmp2.input.StripedHBaseTable.insert(StripedHBaseTable.java:462)
	at com.carrieriq.m2m.platform.mmp3.output.hbase.HBaseDimensionsTable.put(HBaseDimensionsTable.java:151)
	at com.carrieriq.m2m.platform.mmp3.output.DimensionMapper.putDimensionNameValue(DimensionMapper.java:309)
	at com.carrieriq.m2m.platform.mmp3.output.DimNormalizationReducer.onReduce(DimNormalizationReducer.java:465)
	at com.carrieriq.m2m.platform.mmp3.output.DimNormalizationReducer.onReduce(DimNormalizationReducer.java:53)
	at com.carrieriq.m2m.platform.util.hadoop.AbstractReportingReducer.reduce(AbstractReportingReducer.java:23)
	at com.carrieriq.m2m.platform.util.hadoop.AbstractReportingReducer.reduce(AbstractReportingReducer.java:15)
	at org.apache.hadoop.mapred.ReduceTask.runOldReducer(ReduceTask.java:485)
	at org.apache.hadoop.mapred.ReduceTask.run(ReduceTask.java:433)
	at org.apache.hadoop.mapred.Child$4.run(Child.java:268)
	at java.security.AccessController.doPrivileged(Native Method)
	at javax.security.auth.Subject.doAs(Subject.java:396)
	at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1074)
	at org.apache.hadoop.mapred.Child.main(Child.java:262)
{code}

HBase 0.90.2 
                
> 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.
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