hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3692) Handle RejectedExecutionException in HTable
Date Thu, 12 Jan 2012 22:33:39 GMT

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

Jean-Daniel Cryans commented on HBASE-3692:
-------------------------------------------

@Andy,

I tried the attached test (which gave me a hard time with mvn 3.0), by adding some debugging
in HTable I can see that HBasePersistenceHandler repeatedly closes and reuses the same HTables.
That close() method got beefed up it seems during our 0.90 point releases and it now closes
the TPE which generates the rejected execution you see. It also closes the connection to HBase.
The fix would be to not reuse the HTables that are closed.

To add to this jira, we should handle RejectedExecutionException when it comes from a closed
HTable.
                
> 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

        

Mime
View raw message