[jira] [Updated] (KAFKA-13427) Max connections per listener are not blocked

["Ekaterina Chernousova (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-13427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ekaterina Chernousova updated KAFKA-13427:
------------------------------------------
    Priority: Major  (was: Minor)

> Max connections per listener are not blocked
> --------------------------------------------
>
>                 Key: KAFKA-13427
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13427
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.7.0
>            Reporter: Ekaterina Chernousova
>            Priority: Major
>
> According to the documentation, new connections should be blocked if the listener-level limit max connections (listener.name.example.max.connections) is reached except it's an inter-broker listener.
> [http://kafka.apache.org/documentation/#brokerconfigs_max.connections] 
> However, it seems an external listener is treated the same way as inter-broker listener which is connections are being accepted and then some connections with lower priority are closed.
> When I was running some workloads with the listener.name.example.max.connections limit in play, I didn't see any toomanyconnections exceptions, from clients side it was connections were established and disconnected later. 
> After checking the source code [https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/network/SocketServer.scala#L715] I don't see the listener-level max connections limit is being checked before accepting a connection.
>  
> Setting a lower priority as I'm not sure if it's a documentation error or a bug, please let me know if I missed something, thanks!
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)