[
https://issues.apache.org/jira/browse/ZOOKEEPER-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henry Robinson updated ZOOKEEPER-336:
-------------------------------------
Attachment: ZOOKEEPER-336.patch
I've included a C and Java client test in this new patch. I have modified
ZooKeeperServerMain to accept a further optional maxcnxns argument on the
command line in order to be able to write the C test.
Both client tests work by having two clients connect to a server that only
accepts one connection at a time. When the first client connects it is closed,
allowing the second to connect as it retries.
> 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, 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.
