Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0FF92200C46 for ; Wed, 29 Mar 2017 22:57:47 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0EA06160BA0; Wed, 29 Mar 2017 20:57:47 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 5C225160B5D for ; Wed, 29 Mar 2017 22:57:46 +0200 (CEST) Received: (qmail 17602 invoked by uid 500); 29 Mar 2017 20:57:45 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 17584 invoked by uid 99); 29 Mar 2017 20:57:45 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Mar 2017 20:57:45 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id F0A3EC23BE for ; Wed, 29 Mar 2017 20:57:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id PaGnTEMaQMiS for ; Wed, 29 Mar 2017 20:57:44 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id CADE25F2FE for ; Wed, 29 Mar 2017 20:57:43 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 04AD9E06CC for ; Wed, 29 Mar 2017 20:57:43 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id E12092416E for ; Wed, 29 Mar 2017 20:57:41 +0000 (UTC) Date: Wed, 29 Mar 2017 20:57:41 +0000 (UTC) From: "Vladimir Rodionov (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-15227) HBase Backup Phase 3: Fault tolerance (client/server) support MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 29 Mar 2017 20:57:47 -0000 [ https://issues.apache.org/jira/browse/HBASE-15227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov updated HBASE-15227: -------------------------------------- Description: System must be tolerant to faults: # Backup operations MUST be atomic (no partial completion state in system table) # Process must detect any type of failures which can result in a data loss (partial backup) in a backup destination # Proper system table state restore and cleanup must be done in case of a failure # Additional utility to repair backup system table and corresponding file system cleanup must be implemented was:System must be tolerant to faults. Backup operations MUST be atomic (no partial completion state in system table) > HBase Backup Phase 3: Fault tolerance (client/server) support > ------------------------------------------------------------- > > Key: HBASE-15227 > URL: https://issues.apache.org/jira/browse/HBASE-15227 > Project: HBase > Issue Type: Task > Reporter: Vladimir Rodionov > Assignee: Vladimir Rodionov > Priority: Blocker > Labels: backup > Fix For: HBASE-7912 > > Attachments: HBASE-15227-v3.patch, HBASE-15277-v1.patch > > > System must be tolerant to faults: > # Backup operations MUST be atomic (no partial completion state in system table) > # Process must detect any type of failures which can result in a data loss (partial backup) in a backup destination > # Proper system table state restore and cleanup must be done in case of a failure > # Additional utility to repair backup system table and corresponding file system cleanup must be implemented -- This message was sent by Atlassian JIRA (v6.3.15#6346)