You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2015/03/18 19:58:40 UTC

[jira] [Updated] (HBASE-13269) Limit result array preallocation to avoid OOME with large scan caching values

     [ https://issues.apache.org/jira/browse/HBASE-13269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Purtell updated HBASE-13269:
-----------------------------------
    Summary: Limit result array preallocation to avoid OOME with large scan caching values  (was: Remove result array preallocation to avoid OOME with large scan caching values)

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