[ https://issues.apache.org/jira/browse/ZOOKEEPER-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355727#comment-15355727 ]
Arshad Mohammad commented on ZOOKEEPER-2454: -------------------------------------------- yes, you are right, this feature can work by using whole id string, need not to separate out the user and password. But still I feel, not related to this jira, that there should be some mechanism to define what is user in zookeeper. I need this capability for ZOOKEEPER-1260. I created new jira ZOOKEEPER-2456 to handle there. > 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 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)