You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jonathan Hsieh (JIRA)" <ji...@apache.org> on 2014/08/29 19:35:54 UTC

[jira] [Commented] (HBASE-11861) Native MOB Compaction mechanisms.

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

Jonathan Hsieh commented on HBASE-11861:
----------------------------------------

Two straw man suggestions.

1) Integrate the TTL cleaner as a Chore that the master runs periodically (once every 24 hours by default?)

2) Explore ideas to enable a per mob hfile sweep (traverse back to natural hbase row do some sort of bulk load with all the new pointers) so that we can compact without using mr.

> 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
>
> Currenlty, 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.2#6252)