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

Memory leak in MonitoredRPCHandlerImpl

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • 0.92.0
    • 0.92.0, 0.94.0
    • None
    • None
    • Reviewed

    Description

      I got a pretty reliable way of OOME'ing my region servers. Using a big payload (64MB in my case), a default heap and default number of handlers, it's not too long that all the MonitoredRPCHandlerImpl hold on a 64MB reference and once a compaction kicks in it kills everything.

      The issue is that even after the RPC call is done, the packet still lives in MonitoredRPCHandlerImpl.

      Will attach a screen shot of jprofiler's analysis in a moment.

      This is a blocker for 0.92.0, anyone using a high number of handlers and bigish values will kill themselves.

      Attachments

        1. Screen Shot 2012-01-06 at 3.03.09 PM.png
          204 kB
          Jean-Daniel Cryans
        2. HBASE-5141-v2.patch
          1 kB
          Jean-Daniel Cryans
        3. HBASE-5141.patch
          1 kB
          Jean-Daniel Cryans

        Activity

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

          People

            jdcryans Jean-Daniel Cryans
            jdcryans Jean-Daniel Cryans
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment