hadoop-zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Hunt (JIRA)" <j...@apache.org>
Subject [jira] Updated: (ZOOKEEPER-336) single bad client can cause server to stop accepting connections
Date Thu, 07 May 2009 20:06:45 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Patrick Hunt updated ZOOKEEPER-336:
-----------------------------------

    Assignee: Henry Robinson
      Status: Patch Available  (was: Open)

Hi Henry, from your comments it looks like you're ready for review, in ZooKeeper (hadoop in
general) this is indicated
by clicking "submit patch" on the left hand side of the JIRA page. This triggers the review/commit
workflow - in 
particular it will run the hadoop qa bot and let us (committers) know to review for commit.
The process is
documented here:
http://wiki.apache.org/hadoop/ZooKeeper/HowToContribute

It's also fine to submit drafts and ask for review, but I think in this case you are saying
it's ready for final review (correct
me if I"m wrong). One nice thing about submitting is that it's listed on the project page
as "patch available" and ensures
that we won't overlook it.

I will review this presently.


> 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
>
>
> 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.


Mime
View raw message