[
https://issues.apache.org/jira/browse/ZOOKEEPER-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401280#comment-15401280
]
Flavio Junqueira commented on ZOOKEEPER-2454:
---------------------------------------------
[~arshad.mohammad] [~botond.hejj] [~eribeiro] thanks everyone for patch and
reviews. As I'm reading there are two main concerns:
# Absence of support for Netty
# Definition of user (or use id directly?)
what's the current plan? My take is that we need netty support because going
forward folks will be using more the netty option because of, for example, ssl
support. I also think that we need a crisp story around users to avoid problems
with future auth providers. It affects the semantics that the service exposes,
so we need to be extra careful.
It is a great feature, though. We should get it in once we sort out these
issues.
> Limit Connection Count based on User
> ------------------------------------
>
> Key: ZOOKEEPER-2454
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2454
> Project: ZooKeeper
> Issue Type: New Feature
> Components: server
> Reporter: Botond Hejj
> Assignee: Botond Hejj
> Priority: Minor
> Attachments: ZOOKEEPER-2454-br-3-4.patch, ZOOKEEPER-2454.patch,
> ZOOKEEPER-2454.patch
>
>
> ZooKeeper currently can limit connection count from clients coming from the
> same ip. It is a great feature to malfunctioning clients DOS-ing the server
> with many requests.
> I propose additional safegurads for ZooKeeper.
> It would be great if optionally connection count could be limited for a
> specific user or a specific user on an ip.
> This is great in cases where ZooKeeper ensemble is shared by multiple users
> and these users share the same client ips. This can be common in container
> based cloud deployment where external ip of multiple clients can be the same.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
