[HBASE-14241] Fix deadlock during cluster shutdown due to concurrent connection close

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.0.2
• Fix Version/s: 1.0.2, 1.2.0, 1.1.2, 1.3.0, 2.0.0
• Component/s: master, metrics
• Hadoop Flags: Reviewed
• Assignee: Ted Yu
• Reporter: Andrew Kyle Purtell
• Created: 18/Aug/15 19:20
• Updated: 18/Dec/15 00:26
• Resolved: 19/Aug/15 16:02

Description

Caught while testing branch-1.0, shutting down TestMasterMetricsWrapper.

Found one Java-level deadlock:
=============================
"MASTER_META_SERVER_OPERATIONS-ip-10-32-130-237:55342-0":
waiting to lock monitor 0x00007f2a040051c8 (object 0x00000007e36108a8, a org.apache.hadoop.hbase.util.PoolMap),
which is held by "M:0;ip-10-32-130-237:55342"
"M:0;ip-10-32-130-237:55342":
waiting to lock monitor 0x00007f2a04005118 (object 0x00000007e3610b00, a org.apache.hadoop.hbase.ipc.RpcClientImpl$Connection),
which is held by "MASTER_META_SERVER_OPERATIONS-ip-10-32-130-237:55342-0"

Full stack dump and deadlock debug output attached.

Root cause:
In RpcClientImpl#close(), we obtain lock on connections first:

    synchronized (connections) {
      for (Connection conn : connections.values()) {

Then markClosed() tries to obtain lock on connection object:

        if (!conn.isAlive()) {
          conn.markClosed(new InterruptedIOException("RpcClient is closing"));
          conn.close();

Another thread, MetaServerShutdownHandler, calls RpcClientImpl$Connection#setupIOstreams() where :

        markClosed(e);
        close();

Lock on connection object is obtained first, then lock on connections is attempted, leading to deadlock:

      synchronized (connections) {
        connections.removeValue(remoteId, this);
      }