VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.7.0
    • 2.9.0, 3.0.0-alpha4, 2.8.2
    • ipc
    • None
    • 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.branch-2.8.patch
          25 kB
          Daryn Sharp
        2. HADOOP-14035.branch-2.patch
          25 kB
          Daryn Sharp
        3. HADOOP-14035.patch
          25 kB
          Daryn Sharp

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            daryn Daryn Sharp
            daryn Daryn Sharp
            Votes:
            0 Vote for this issue
            Watchers:
            13 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment