hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nate Putnam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3421) Very wide rows -- 30M plus -- cause us OOME
Date Tue, 20 Sep 2011 17:49:09 GMT

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

Nate Putnam commented on HBASE-3421:
------------------------------------

Sorry about that. My mistake, I should be more careful when creating patches. v4 is the winner.
Thanks for your patience. 

> Very wide rows -- 30M plus -- cause us OOME
> -------------------------------------------
>
>                 Key: HBASE-3421
>                 URL: https://issues.apache.org/jira/browse/HBASE-3421
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.90.0
>            Reporter: stack
>         Attachments: HBASE-3421.patch, HBASE-34211-v2.patch, HBASE-34211-v3.patch
>
>
> From the list, see 'jvm oom' in http://mail-archives.apache.org/mod_mbox/hbase-user/201101.mbox/browser,
it looks like wide rows -- 30M or so -- causes OOME during compaction.  We should check it
out. Can the scanner used during compactions use the 'limit' when nexting?  If so, this should
save our OOME'ing (or, we need to add to the next a max size rather than count of KVs).

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

        

Mime
View raw message