[
https://issues.apache.org/jira/browse/HBASE-13269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14367715#comment-14367715
]
Hadoop QA commented on HBASE-13269:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12705413/HBASE-13269-1.0.patch
against master branch at commit f9a17edc252a88c5a1a2c7764e3f9f65623e0ced.
ATTACHMENT ID: 12705413
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/13296//console
This message is automatically generated.
> 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)
