[
https://issues.apache.org/jira/browse/KAFKA-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14264667#comment-14264667
]
Joe Stein commented on KAFKA-1512:
----------------------------------
I was just about to commit this and realized this is introduced in 0.8.2 but
not fully complete so we should have this as a patch for 0.8.2 and trunk.
[~jholoman] can you upload a 0.8.2 patch also so we can double commit this to
0.8.2 and trunk please... if there are no objects to having this in 0.8.2 it
seems reasonable since it was introduced in this release we shouldn't ship
something not complete if we have fix available now.
> 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
> Affects Versions: 0.8.2
> Reporter: Jay Kreps
> Assignee: Jeff Holoman
> Fix For: 0.8.2
>
> Attachments: KAFKA-1512.patch, KAFKA-1512.patch,
> KAFKA-1512_2014-07-03_15:17:55.patch, KAFKA-1512_2014-07-14_13:28:15.patch,
> KAFKA-1512_2014-12-23_21:47:23.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.3.4#6332)
