[HBASE-6956] Do not return back to HTablePool closed connections

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 0.90.6
• Component/s: Client
• Assignee: Unassigned
• Reporter: Igor Yurinok
• Created: 05/Oct/12 10:10
• Updated: 14/Jun/22 21:53
• Resolved: 16/Nov/16 22:30

Description

Sometimes we see a lot of Exception about closed connections:

 org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@553fd068 closed
org.apache.hadoop.hbase.client.ClosedConnectionException: org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@553fd068 closed

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

Issue Links

• relates to: HBASE-6651 Improve thread safety of HTablePool
• relates to: HBASE-6580 Deprecate HTablePool in favor of HConnection.getTable(...)