zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Flavio Junqueira (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2454) Limit Connection Count based on User
Date Sun, 07 Aug 2016 16:54:20 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410988#comment-15410988

Flavio Junqueira commented on ZOOKEEPER-2454:

I really don't mind splitting up the work into multiple jiras, it is actually good for review
purposes, but I'm concerned that it will be weird if we have the feature in a release for
NIO and not for the Netty option.

> 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

View raw message