VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.7.0
    • Fix Version/s: 2.9.0, 3.0.0-alpha4, 2.8.2
    • Component/s: ipc
    • Labels:
      None
    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      Description

      When fcq backoff is enabled and an abusive client overflows the call queue, its connection is closed, as well as subsequent good client connections. Disconnects are very disruptive, esp. to multi-threaded clients with multiple outstanding requests, or clients w/o a retry proxy (ex. datanodes).

      Until the abusive user is downgraded to a lower priority queue, disconnect/reconnect mayhem occurs which significantly degrades performance. Server metrics look good despite horrible client latency.

      The fcq should utilize selective ipc disconnects to avoid pushback disconnecting good clients.

        Attachments

        1. HADOOP-14035.patch
          25 kB
          Daryn Sharp
        2. HADOOP-14035.branch-2.patch
          25 kB
          Daryn Sharp
        3. HADOOP-14035.branch-2.8.patch
          25 kB
          Daryn Sharp

        Issue Links

          Activity

            People

            • Assignee:
              daryn Daryn Sharp
              Reporter:
              daryn Daryn Sharp

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment