[ https://issues.apache.org/jira/browse/ZOOKEEPER-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flavio Paiva Junqueira updated ZOOKEEPER-336: --------------------------------------------- Status: Open (was: Patch Available) > single bad client can cause server to stop accepting connections > ---------------------------------------------------------------- > > Key: ZOOKEEPER-336 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-336 > Project: Zookeeper > Issue Type: Improvement > Components: c client, java client, server > Reporter: Patrick Hunt > Assignee: Henry Robinson > Priority: Critical > Fix For: 3.2.0 > > Attachments: ZOOKEEPER-336.patch, ZOOKEEPER-336.patch, > ZOOKEEPER-336.patch, ZOOKEEPER-336.patch > > > One user saw a case where a single mis-programmed client was overloading the > server with connections - the client was creating a huge number of sessions > to the server. This caused all of the fds on the server to become used. > Seems like we should have some way of limiting (configurable override) the > maximum number of sessions from a single client (say 10 by default?) Also we > should output warnings when this limit is exceeded (or attempt to exceed). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.