Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 98A041834B for ; Thu, 17 Mar 2016 18:28:34 +0000 (UTC) Received: (qmail 63327 invoked by uid 500); 17 Mar 2016 18:28:33 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 62924 invoked by uid 500); 17 Mar 2016 18:28:33 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 62894 invoked by uid 99); 17 Mar 2016 18:28:33 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Mar 2016 18:28:33 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 8DE072C1F56 for ; Thu, 17 Mar 2016 18:28:33 +0000 (UTC) Date: Thu, 17 Mar 2016 18:28:33 +0000 (UTC) From: "Vladimir Rodionov (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (HBASE-15443) HBase Backup Phase 2: Multiple backup destinations support (data model) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-15443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Rodionov resolved HBASE-15443. --------------------------------------- Resolution: Fixed Part of HBASE-14123 patch v12. > HBase Backup Phase 2: Multiple backup destinations support (data model) > ----------------------------------------------------------------------- > > Key: HBASE-15443 > URL: https://issues.apache.org/jira/browse/HBASE-15443 > Project: HBase > Issue Type: Bug > Reporter: Vladimir Rodionov > Assignee: Vladimir Rodionov > > The current implementation (implicitly) implies the single backup destination (when we make decision in BackupLogCleaner if WAL file is eligible for deletion we do not check if WAL file has been copied over to ALL possible backup destinations) > This JIRA is to make Phase 2 data structure/model/layout to be compatible with this feature in a future. The feature itself is going to be part of Phase 3. -- This message was sent by Atlassian JIRA (v6.3.4#6332)