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

Posted to issues@hbase.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2011/09/13 06:53:08 UTC

[jira] [Commented] (HBASE-4380) large scan caching size causes RS to throw OOME

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

Jean-Daniel Cryans commented on HBASE-4380:
-------------------------------------------

Dupe of HBASE-2506?

> large scan caching size causes RS to throw OOME
> -----------------------------------------------
>
>                 Key: HBASE-4380
>                 URL: https://issues.apache.org/jira/browse/HBASE-4380
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>            Reporter: Ming Ma
>            Assignee: Ming Ma
>
> If the hbase application specifies a large caching size via Scan.setCaching(...),  RS will try to accumulate enough rows before returning to the client. This could blow up RS memory. In TableInputFormat scenario, we have couple mappers with large caching size, thus RS memory usage goes up quickly.
> RS perhaps should take memory usage into account, for example, return less results per HRegionInterface.next(long scannerId, int numberOfRows) call in the case of low memory.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira