hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-6956) Do not return back to HTablePool closed connections
Date Wed, 16 Nov 2016 22:30:59 GMT

     [ https://issues.apache.org/jira/browse/HBASE-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

stack resolved HBASE-6956.
    Resolution: Not A Problem

No longer a problem. We don't do connections in the 0.90-way.

> Do not return back to HTablePool closed connections
> ---------------------------------------------------
>                 Key: HBASE-6956
>                 URL: https://issues.apache.org/jira/browse/HBASE-6956
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 0.90.6
>            Reporter: Igor Yurinok
> Sometimes we see a lot of Exception about closed connections:
> {code}
>  org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@553fd068
> org.apache.hadoop.hbase.client.ClosedConnectionException: org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@553fd068
> {code}
> After investigation we assumed that it occurs because closed connection returns back
into HTablePool. 
> For our opinion best solution is  check whether the table is closed in method HTablePool.putTable
and if true don't add it into the queue and release such HTableInterface.
> But unfortunatly right now there are no access to HTable#closed field through HTableInterface

This message was sent by Atlassian JIRA

View raw message