[
https://issues.apache.org/jira/browse/HBASE-11861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14296336#comment-14296336
]
Jingcheng Du commented on HBASE-11861:
--------------------------------------
Thanks [~anoopsamjohn] and [~jmhsieh] for the comments.
bq. Now the actual compaction is done by the chore thread itself. Instead the
actual compact operation can be given to a pool of threads?
I was thinking that. It's worth a try. Compact different partitions
concurrently. What's your opinion for this? [~jmhsieh] and [~ram_krish]. Thanks.
> Native MOB Compaction mechanisms.
> ---------------------------------
>
> Key: HBASE-11861
> URL: https://issues.apache.org/jira/browse/HBASE-11861
> Project: HBase
> Issue Type: Sub-task
> Components: regionserver, Scanners
> Affects Versions: 2.0.0
> Reporter: Jonathan Hsieh
> Assignee: Jingcheng Du
> Attachments: 141030-mob-compaction.pdf, HBASE-11861-V1.diff,
> HBASE-11861-V2.diff, HBASE-11861.diff, mob compaction-out-of-region.pdf, mob
> compaction.pdf
>
>
> Currently, the first cut of mob will have external processes to age off old
> mob data (the ttl cleaner), and to compact away deleted or over written data
> (the sweep tool).
> From an operational point of view, having two external tools, especially one
> that relies on MapReduce is undesirable. In this issue we'll tackle
> integrating these into hbase without requiring external processes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
