[
https://issues.apache.org/jira/browse/HBASE-11861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14293278#comment-14293278
]
Anoop Sam John commented on HBASE-11861:
----------------------------------------
Left some comments in RB
major issue/Qs..
Now the actual compaction is done by the chore thread itself. Instead the
actual compact operation can be given to a pool of threads?
The compaction work is done by master! Can this be distributed to RSs. (Even
when we have multi threaded MOB compaction, we have to make sure that all the
compaction is not running at once which will cause high IO)
We will have to give Admin APIs and shell support for the MOB compaction?
> 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)
