You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@zookeeper.apache.org by "Mohammad Arshad (Jira)" <ji...@apache.org> on 2019/10/01 09:50:00 UTC
[jira] [Assigned] (ZOOKEEPER-2238) Support limiting the maximum
number of connections/clients to a zookeeper server.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mohammad Arshad reassigned ZOOKEEPER-2238:
------------------------------------------
Assignee: (was: Mohammad Arshad)
> 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
> Priority: Major
> Labels: pull-request-available
> Attachments: ZOOKEEPER-2238-05.patch, ZOOKEEPER-2238-06.patch, ZOOKEEPER-2238-07.patch, ZOOKEEPER-2238.2.patch, ZOOKEEPER-2238.3.patch, ZOOKEEPER-2238.4.patch, ZOOKEEPER-2238.diff
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)