[
https://issues.apache.org/jira/browse/HBASE-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109109#comment-13109109
]
Hudson commented on HBASE-3421:
-------------------------------
Integrated in HBase-0.92 #6 (See [https://builds.apache.org/job/HBase-0.92/6/])
HBASE-3421 Very wide rows -- 30M plus -- cause us OOME (Nate Putnam)
tedyu :
Files :
* /hbase/branches/0.92/CHANGES.txt
*
/hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/Store.java
> 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
> Assignee: Nate Putnam
> Fix For: 0.90.5
>
> Attachments: HBASE-3421.patch, HBASE-34211-v2.patch,
> HBASE-34211-v3.patch, HBASE-34211-v4.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
