[
https://issues.apache.org/jira/browse/HBASE-6728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482852#comment-13482852
]
Lars Hofhansl commented on HBASE-6728:
--------------------------------------
I actually misread the patch. It checks the *current* size (not the current
size + what is being added).
So in my example above it would add the 2g response to the queue, but then
block other responses until that one is done. This seems fine.
> [89-fb] prevent OOM possibility due to per connection responseQueue being
> unbounded
> -----------------------------------------------------------------------------------
>
> Key: HBASE-6728
> URL: https://issues.apache.org/jira/browse/HBASE-6728
> Project: HBase
> Issue Type: Bug
> Reporter: Kannan Muthukkaruppan
> Assignee: Michal Gregorczyk
> Fix For: 0.94.3, 0.96.0
>
> Attachments: 6728.94, 6728-trunk.txt
>
>
> 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.]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
