[HADOOP-18534] Propose a mechanism to free the direct memory occupied by RPC Connections

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: rpc-server
• Target Version/s: 3.5.0
• Assignee: Unassigned
• Reporter: asdfgh19
• Created: 21/Nov/22 05:22
• Updated: 04/Jan/24 09:49

Description

  In the RPC Client, a thread called RpcRequestSender is responsible for writing the connection request to the socket. Every time a request is sent, a direct memory is applied for in sun.nio.ch.IOUtil#write() and cached.

  If Connection and RpcRequestSender are promoted to the old generation, they will not be recycled when full gc is not performed, resulting in the DirectByteBuffer cached in sun.nio.ch.Util not being recycled. When the memory occupied by DirectByteBuffer is too large, the jvm process may not have the opportunity to do full gc and is killed.

  Unfortunately, there is no easy way to free these DirectByteBuffers. Perhaps, we can manually free these DirectByteBuffers by the following methods when the Connection is closed.

private void freeDirectBuffer() {
  try {
    DirectBuffer buffer = (DirectBuffer) Util.getTemporaryDirectBuffer(1);
    buffer.cleaner().clean();
  } catch (Throwable t) {
    LOG.error("free direct memory error, connectionId: " + remoteId, t);
  }
}