[
https://issues.apache.org/jira/browse/HBASE-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012329#comment-13012329
]
Subbu M Iyer commented on HBASE-3692:
-------------------------------------
It seems to me that this one is coming out from HTable's ThreadPoolExecutor
during batch calls/or flush. May be we can add a RejectedExecutionHandler and
handle this exception gracefully with proper message to the caller.
I am seeing that this could pop-out in all the places where we use
ThreadPoolExecutor and may be we need a global policy on how to address
rejected execution requests?
> 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
