[
https://issues.apache.org/jira/browse/HBASE-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623043#action_12623043
]
Billy Pearson commented on HBASE-775:
-------------------------------------
I thought we did it in Ram if its just streaming then there should not be a
max. we should do all we can on each compaction that would be less work on the
next compaction. I assume there some kind of index that is in memory so we keep
track of max versions etc so that would be the only factor to limit the count
or size of the compaction.
Sense we do not compact in memory I do not see any reason for this issue then
so it would be resolved as won't fix
HBASE-64 should also be resolved as HBASE 785 solved that problem
> max mapfiles to compact at one time
> -----------------------------------
>
> Key: HBASE-775
> URL: https://issues.apache.org/jira/browse/HBASE-775
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: regionserver
> Reporter: Billy Pearson
> Assignee: Billy Pearson
> Priority: Blocker
> Fix For: 0.2.1, 0.3.0
>
> Attachments: 775-patch.txt
>
>
> Currently we compact all map files with no upper limit this could cause a
> regionserver to OOME if the compaction get behind and the number of mapfiles
> build up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.