Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
MIME-Version: 1.0
In-Reply-To: <CAAg3a2ovHdekL3ScB2igZV4CnwJ8z9XKGL=mvKTO9wo_PTF+3w@mail.gmail.com>
References: <CAAg3a2ovHdekL3ScB2igZV4CnwJ8z9XKGL=mvKTO9wo_PTF+3w@mail.gmail.com>
From: Andrew Purtell <apurtell@apache.org>
Date: Fri, 10 Mar 2017 11:16:46 -0800
Message-ID: <CA+RK=_DVfbzvc9hQw-GUwzJ02t=PAtKETOa_uKpQ5VOVuOm6vA@mail.gmail.com>
Subject: Re: [VOTE] Backup/Restore feature for HBase 2.0, vote closing 3/11/2017
To: "dev@hbase.apache.org" <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary=001a11401350507713054a6536ba
archived-at: Fri, 10 Mar 2017 19:17:30 -0000

--001a11401350507713054a6536ba
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

> Only BLOCKERs and CRITICALs are guaranteed for HBase 2.0 release.

If we have identified blockers, why merge this before they are in?
Otherwise we can't release 2.0, and it is overdue.


On Wed, Mar 8, 2017 at 1:32 PM, Vladimir Rodionov <vladrodionov@gmail.com>
wrote:

> Hello, HBase folks
>
> For your consideration today is Backup/Restore feature for Apache HBAse
> 2.0.
> Backup code is available as a mega patch in HBASE-14123 (v61), applies
> cleanly to the current master, all test PASS, patch has no other issues.
>
> The patch has gone through numerous rounds of code reviews and has probab=
ly
> the most lengthy discussion thread on Apache JIRA (HBASE-14123) :)
>
> The work has been split into 3 phases (HBASE-14030, 14123, 14414) Two fir=
st
> are complete, third one is still in progress.
>
>
> *** Summary of work HBASE-14123
>
> The new feature introduces new command-line extensions to the hbase comma=
nd
> and, from the client side, is accessible through command-line only
> Operations:
> * Create full backup on a list of tables or backup set
> * Create incremental backup image for table list or backup set
> * Restore list of tables from a given backup image
> * Show current backup progress
> * Delete backup image and all related images
> * Show history of backups
> * Backup set operations: create backup set, add/remove table to/from back=
up
> set, etc
>
> In the current implementation, the feature is already usable, meaning tha=
t
> users can backup tables and restore them using provided command-line tool=
s.
> Both: full and incremental backups are supported.
> This work is based on original work of IBM team (HBASE-7912). The full li=
st
> of JIRAs included in this mega patch can be found in three umbrella JIRAs=
:
> HBASE-14030 (Phase 1), HBASE-14123 (Phase 2) and HBASE-14414 (Phase 3 - a=
ll
> resolved ones made it into the patch)
>
> *** What are the remaining work items
>
> All remaining items can be found in Phase 3 umbrella JIRA: HBASE-14414.
> They are split into 3 groups: BLOCKER, CRITICAL, MAJOR
> Only BLOCKERs and CRITICALs are guaranteed for HBase 2.0 release.
>
> ***** BLOCKER
>
> * HBASE-14417 Incremental backup and bulk loading ( Patch available)
> * HBASE-14135 HBase Backup/Restore Phase 3: Merge backup images
> * HBASE-14141 HBase Backup/Restore Phase 3: Filter WALs on backup to
> include only edits from backup tables (Patch available)
> * HBASE-17133 Backup documentation
> * HBASE-15227 Fault tolerance support
>
> ***** CRITICAL
>
> * HBASE-16465 Disable split/merges during backup
>
> We have umbrella JIRA (HBASE-14414) to track all the remaining work
> All the BLOCKER and CRITICAL JIRAs currently in open state will be
> implemented by 2.0 release time. Some MAJOR too, but it depends on resour=
ce
> availability
> The former development branch (HBASE-7912) is obsolete and will be
> closed/deleted after the merge.
> We want backup to be a GA feature in 2.0
> We are going to support full backward compatibility for backup tool in 2.=
0
> and onwards.
>
> **** Configuration
>
> Backup is disabled, by default. To enable it, the following configuration
> properties must be added to hbase-site.xml:
>
> hbase.backup.enable=3Dtrue
> hbase.master.logcleaner.plugins=3DYOUR_PLUGINS,org.
> apache.hadoop.hbase.backup.master.BackupLogCleaner
> hbase.procedure.master.classes=3DYOUR_CLASSES,org.
> apache.hadoop.hbase.backup.master.LogRollMasterProcedureManager
> hbase.procedure.regionserver.classes=3DYOUR_CLASSES,org.
> apache.hadoop.hbase.backup.regionserver.LogRollRegionServerProcedureMa
> nager
>
>
> I would like to thank IBM team and Jerry He for original work,
>
> Enis, Ted, Stack, Matteo, Jerry for time spent on code reviews
>
> Special thanks to Ted Yu for his co-development work.
>
> References:
>
> https://issues.apache.org/jira/browse/HBASE-7912 (original IBM, contains
> design doc)
> https://issues.apache.org/jira/browse/HBASE-14030 (Phase 1)
> https://issues.apache.org/jira/browse/HBASE-14123 (Phase 2)
> https://issues.apache.org/jira/browse/HBASE-14414 (Phase 3)
>
> Please  vote +1/-1 by midnight Pacific Time (00:00
> -0800 GMT) on March 11th  =E2=80=8Bon whether or not we should merge this=
 into the
> current master.
>
> -Vladimir Rodionov
>


--=20
Best regards,

   - Andy

If you are given a choice, you believe you have acted freely. - Raymond
Teller (via Peter Watts)

--001a11401350507713054a6536ba--