[ https://issues.apache.org/jira/browse/HBASE-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487013#comment-13487013 ]
Ted Yu commented on HBASE-6956: ------------------------------- For putTable(), I see this javadoc: {code} /** * This method is not needed anymore, clients should call * HTableInterface.close() rather than returning the tables to the pool * * @param table * the proxy table user got from pool * @deprecated */ public void putTable(HTableInterface table) throws IOException { {code} @Igor, @Shengjie: Can you tell us whether you followed the above suggestion ? Thanks > 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