hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Igor Yurinok (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-6956) Do not return back to HTablePool closed connections
Date Fri, 05 Oct 2012 10:12:03 GMT
Igor Yurinok created HBASE-6956:
-----------------------------------

             Summary: 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 closed
org.apache.hadoop.hbase.client.ClosedConnectionException: org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@553fd068
closed
{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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message