[HBASE-10396] The constructor of HBaseAdmin may close the shared HConnection

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 0.94.16
• Component/s: Admin, Client
• Assignee: Unassigned
• Reporter: Jianwei Cui
• Created: 22/Jan/14 08:53
• Updated: 17/Jun/22 05:01
• Resolved: 12/Apr/17 04:19

Description

HBaseAdmin has the constructor:

  public HBaseAdmin(Configuration c)
  throws MasterNotRunningException, ZooKeeperConnectionException {
    this.conf = HBaseConfiguration.create(c);
    this.connection = HConnectionManager.getConnection(this.conf);
    ...

As shown in above code, HBaseAdmin will get a cached HConnection or create a new HConnection and use this HConnection to connect to Master. Then, HBaseAdmin will delete the HConnection when connecting to master fail as follows:

    while ( true ){
      try {
        this.connection.getMaster();
        return;
      } catch (MasterNotRunningException mnre) {
        HConnectionManager.deleteStaleConnection(this.connection);
        this.connection = HConnectionManager.getConnection(this.conf);
      }

The above code will invoke HConnectionManager#deleteStaleConnection to delete the HConnection from global HConnection cache. The risk is that the deleted HConnection might be sharing by other threads, such as HTable or HTablePool. Then, these threads which sharing the deleted HConnection will get closed HConnection exception:

org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation@61bc59aa closed

If users use HTablePool, the situation will become worse because closing HTable will only return HTable to HTablePool which won't reduce the reference count of the closed HConnection. Then, the closed HConnection will always be used before clearing HTablePool. In 0.94, some modules such as Rest server are using HTablePool, therefore may suffer from this problem.