[
https://issues.apache.org/jira/browse/HBASE-6728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481962#comment-13481962
]
Hudson commented on HBASE-6728:
-------------------------------
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #231 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/231/])
HBASE-6728 revert (Revision 1401012)
HBASE-6728 prevent OOM possibility due to per connection responseQueue being
unbounded (Revision 1401008)
Result = FAILURE
tedyu :
Files :
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/HBaseServer.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/metrics/RegionServerDynamicMetrics.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/SizeBasedThrottler.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestSizeBasedThrottler.java
tedyu :
Files :
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/HBaseServer.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/metrics/RegionServerDynamicMetrics.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/SizeBasedThrottler.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/util/TestSizeBasedThrottler.java
> [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.96.0
>
> Attachments: 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
