hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13269) Limit result array preallocation to avoid OOME with large scan caching values
Date Tue, 17 Mar 2015 22:03:39 GMT

    [ https://issues.apache.org/jira/browse/HBASE-13269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14366180#comment-14366180
] 

Andrew Purtell commented on HBASE-13269:
----------------------------------------

bq. otherwise it may just be best to remove the preallocation all together.

This is exactly what I was thinking too and I'm testing out a patch now (although almost certainly
every test will pass)

> 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
>
>
> 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)

Mime
View raw message