...
kafka.network:type=Acceptor,name=AcceptorIdlePercentAcceptorBlockedPercent,listener={listenerName}
A new broker configuration option will be added to limit the total number of connections that may be active on the broker at any time. This is in addition to the existing max.connections.per.ip
config that will continue to limit the number of connections from each host ip address. When the limit is reached, new connections will not be accepted until one or more existing connections are closed. This will be a dynamic broker-wide config that can be updated without restarting the broker.
...
The connection queue for Processors
will be changed to ArrayBlockingQueue
with a fixed size of 20
. Acceptor will use round-robin allocation to allocate each new connection to the next available Processor
to which the connection can be added without blocking. If a Processor
's queue is full, the next Processor
will be chosen. If the connection queue on all Processors
are full, Acceptor
blocks until the connection can be added to the selected Processor
. No new connections will be accepted during this period. The amount of time Acceptor
is blocked can be monitored using the new AcceptorIdlePercent
AcceptorBlockedPercent
metric.
Acceptor
will stop accepting new connections when the broker's max.connections
limit is reached. New connections will be accepted as soon as a connection is closed by any of the Processors
. Acceptor
will also stop accepting new connections when its listener's listener.name.{listener}.max.connections
limit is reached. New connections will be accepted as soon as a connection is closed by any of the Processors
of that listener. Inter-broker connections will be protected in multi-listener brokers by closing client connections to accommodate inter-broker connections. Any time spent by Acceptor
waiting for connections to close will also be included in the new AcceptorIdlePercent
AcceptorBlockedPercent
metric. The existing max.connections.per.ip
config will be applied without any changes. Connections dropped due to hitting the per-ip limit will not appear in the AcceptorIdlePercent
AcceptorBlockedPercent
metric since these connections are accepted and then dropped.
...