Rajini Sivaram created KAFKA-7454:
-------------------------------------
Summary: Use lazy allocation for SslTransportLayer buffers
Key: KAFKA-7454
URL: https://issues.apache.org/jira/browse/KAFKA-7454
Project: Kafka
Issue Type: Improvement
Components: security
Affects Versions: 2.0.0, 1.1.1, 1.0.2, 0.11.0.3
Reporter: Rajini Sivaram
Assignee: Rajini Sivaram
Fix For: 2.1.0
At the moment, three heap buffers are allocated for SslTransportLayers at the
time when the instance is created (before establishing the connection on the
client-side and when accepting the connection on the broker-side). When there
are a large number of connections and the broker is overloaded, this can result
in unnecessary memory pressure on the broker due to client reconnections since
buffers may be allocated unnecessarily for client connections whose handshake
is never processed. It will be better to lazily allocate buffers to reduce
memory pressure. On the broker-side, buffers will be allocated when the first
packet is received from the client, starting handshake. On the client-side,
buffers will be allocated once the connection is established when the client
initiates handshake.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)