You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Igor Soarez (JIRA)" <ji...@apache.org> on 2019/06/07 13:08:00 UTC

[jira] [Created] (KAFKA-8505) Limit the maximum number of connections per ip client ID

Igor Soarez created KAFKA-8505:
----------------------------------

             Summary: Limit the maximum number of connections per ip client ID
                 Key: KAFKA-8505
                 URL: https://issues.apache.org/jira/browse/KAFKA-8505
             Project: Kafka
          Issue Type: New Feature
            Reporter: Igor Soarez


As highlighted by KAFKA-1512 back in 2014, it is important to be able to limit the number of client connections to brokers to maintain service availability. With multiple use-cases on the same cluster, it's important to prevent one misconfigured use-case from affecting other use-cases.

Cloud infrastructure technology has come a long way since then. Nowadays days in a private network using container orchestration technology, IPs come cheap. Limiting connections solely on origin IP is no longer acceptable.

Kafka needs to support connection limits based on client identity.

A new configuration property - {{max.connections.per.clientid}} - should work similarly to {{max.connections.per.ip}} using ConnectionQuotas, managed straight after parsing the request header in SocketServer.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)