[
https://issues.apache.org/jira/browse/ZOOKEEPER-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Ribeiro updated ZOOKEEPER-2238:
--------------------------------------
Attachment: ZOOKEEPER-2238.diff
Hi [~nijel],
Yes, I have started worked on it. I am attaching a current snapshot of the
patch (WORK IN PROGRESS). It works on NIOServerFactory connections already (see
zoo_sample.conf), but I need to write unit tests and port it to the
NettyServerFactory (Netty class lacks a lot of functionally wrt NIO, it doesn't
even support max client connections, afaik).
You can play with the patch, but it's not finished yet. Let me know if you find
any bug or any chance of improvement (I have no problem co-authoring it with
you). ;)
Cheers!
> Support limiting the maximum number of connections/clients to a zookeeper
> server.
> ---------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2238
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2238
> Project: ZooKeeper
> Issue Type: Improvement
> Reporter: nijel
> Assignee: Edward Ribeiro
> Attachments: ZOOKEEPER-2238.diff
>
>
> Currently zookeeper have the feature of limiting the maximum number of
> connection/client per IP or Host (maxClientCnxns).
> But to safe guard zookeeper server from DoS attack due to many clients from
> different IPs, it is better to have a limit of total number of
> connections/clients to a a single member of the ZooKeeper ensemble as well.
> So the idea is to introduce a new configuration to limit the maximum number
> of total connections/clients.
> Please share your thoughts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
