[
https://issues.apache.org/jira/browse/KAFKA-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051899#comment-14051899
]
Jay Kreps edited comment on KAFKA-1512 at 7/3/14 8:46 PM:
----------------------------------------------------------
A proposal from the LI ops team is to also add an override for this so you can
have custom limits for ips if you want:
{code}
max.connections.per.ip.overrides=192.168.1.1:5, 192.168.1.2:, 192.168.1.3:45
{code}
If no objections I will implement this too.
was (Author: jkreps):
A proposal from the LI ops team is to also add an override for this so you can
have custom limits for ips if you want
max.connections.per.ip.overrides=192.168.1.1:5, 192.168.1.2:, 192.168.1.3:45
If no objections I will implement this too.
> Limit the maximum number of connections per ip address
> ------------------------------------------------------
>
> Key: KAFKA-1512
> URL: https://issues.apache.org/jira/browse/KAFKA-1512
> Project: Kafka
> Issue Type: New Feature
> Reporter: Jay Kreps
> Assignee: Jay Kreps
> Attachments: KAFKA-1512.patch, KAFKA-1512.patch
>
>
> To protect against client connection leaks add a new configuration
> max.connections.per.ip
> that causes the SocketServer to enforce a limit on the maximum number of
> connections from each InetAddress instance. For backwards compatibility this
> will default to 2 billion.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
