[
https://issues.apache.org/jira/browse/HBASE-5141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181705#comment-13181705
]
Todd Lipcon commented on HBASE-5141:
------------------------------------
Yep, sorry, the memory budgeting would have to be before the data is read into
the queue in the IPC server.
I agree that nulling out the rpc packet will fix the issue as reported here.
Just saying that the issue doesn't seem likely to affect most use cases where
RPCs are of mixed size and where people have already budgeted their heap to fit
a bunch of calls.
> Memory leak in MonitoredRPCHandlerImpl
> --------------------------------------
>
> Key: HBASE-5141
> URL: https://issues.apache.org/jira/browse/HBASE-5141
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.92.0
> Reporter: Jean-Daniel Cryans
> Priority: Blocker
> Fix For: 0.92.0, 0.94.0
>
> Attachments: Screen Shot 2012-01-06 at 3.03.09 PM.png
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
