Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-6728

[89-fb] prevent OOM possibility due to per connection responseQueue being unbounded

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.94.3
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      Reviewed
    • Release Note:
      Hide
      This issue adds config parameter, ipc.server.response.queue.maxsize, to control the maximum size of response queue.
      Default response queue max size is 1GB.
      Show
      This issue adds config parameter, ipc.server.response.queue.maxsize, to control the maximum size of response queue. Default response queue max size is 1GB.

      Description

      The per connection responseQueue is an unbounded queue. The request handler threads today try to send the response in line, but if things start to backup, the response is sent via a per connection responder thread. This intermediate queue, because it has no bounds, can be another source of OOMs.

      [Have not looked at this issue in trunk. So it may or may not be applicable there.]

        Attachments

        1. 6728.94
          21 kB
          Ted Yu
        2. 6728-trunk.txt
          26 kB
          Ted Yu

          Issue Links

            Activity

              People

              • Assignee:
                michalgr Michal Gregorczyk
                Reporter:
                kannanm Kannan Muthukkaruppan
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: