[
https://issues.apache.org/jira/browse/KAFKA-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257869#comment-14257869
]
Jeff Holoman commented on KAFKA-1512:
-------------------------------------
I modified the two tests related to max connections in the SocketServerTest
class a bit. Basically I'm just checking if the socket inpustream is still
open, rather than sending a request through. I found in testing that isolating
the tests to only test socketServer functionality was a bit hard and that
sending real requests would be beneficial. I did not modify the other tests in
SocketServerTest, though I think that utilizing the ClusterMetadataRequest in
the tests rather than bogus and / or empty producer requests may be worth
looking into.
> 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: 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)
