Uploaded image for project: 'ZooKeeper'
  1. ZooKeeper
  2. ZOOKEEPER-336

single bad client can cause server to stop accepting connections

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • None
    • 3.2.0
    • c client, java client, server
    • None
    • Reviewed

    Description

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

      Attachments

        1. ZOOKEEPER-336.patch
          8 kB
          Henry Robinson
        2. ZOOKEEPER-336.patch
          13 kB
          Henry Robinson
        3. ZOOKEEPER-336.patch
          14 kB
          Patrick D. Hunt
        4. ZOOKEEPER-336.patch
          18 kB
          Henry Robinson
        5. ZOOKEEPER-336.patch
          30 kB
          Henry Robinson
        6. ZOOKEEPER-336.patch
          30 kB
          Benjamin Reed

        Activity

          People

            henryr Henry Robinson
            phunt Patrick D. Hunt
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: