[
https://issues.apache.org/jira/browse/HBASE-13269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14368272#comment-14368272
]
Hudson commented on HBASE-13269:
--------------------------------
FAILURE: Integrated in HBase-1.0 #812 (See
[https://builds.apache.org/job/HBase-1.0/812/])
HBASE-13269 Limit result array preallocation to avoid OOME with large scan
caching values (apurtell: rev d443c7096fced912b8d0cc5c63f9f013762e6122)
*
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java
> Limit result array preallocation to avoid OOME with large scan caching values
> -----------------------------------------------------------------------------
>
> Key: HBASE-13269
> URL: https://issues.apache.org/jira/browse/HBASE-13269
> Project: HBase
> Issue Type: Bug
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 1.0.1, 0.98.12
>
> Attachments: HBASE-13269-0.98.patch, HBASE-13269-0.98.patch,
> HBASE-13269-1.0.patch, HBASE-13269-1.0.patch
>
>
> Scan#setCaching(Integer.MAX_VALUE) will likely terminate the regionserver
> with an OOME due to preallocation of the result array according to this
> parameter. We should limit the preallocation to some sane value. Definitely
> affects 0.98 (fix needed to HRegionServer) and 1.0.x (fix needed to
> RsRPCServices), not sure about later versions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
