Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 5 Dec 2014 08:31:13 +0000 (UTC)
From: "Jingcheng Du (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12737853.1409333285000.82527.1417768273268@Atlassian.JIRA>
In-Reply-To: <JIRA.12737853.1409333285000@Atlassian.JIRA>
References: <JIRA.12737853.1409333285000@Atlassian.JIRA>
 <JIRA.12737853.1409333285298@arcas>
Subject: [jira] [Commented] (HBASE-11861) Native MOB Compaction mechanisms.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jingcheng Du commented on HBASE-11861:
--------------------------------------

Hi Jon [~jon@cloudera.com], do you want to look at the high level design for the mob compaction? 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
>         Attachments: 141030-mob-compaction.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)