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 40A8B200D2D for ; Fri, 27 Oct 2017 09:26:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3F3F9160BF6; Fri, 27 Oct 2017 07:26:09 +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 855131609E9 for ; Fri, 27 Oct 2017 09:26:08 +0200 (CEST) Received: (qmail 48999 invoked by uid 500); 27 Oct 2017 07:26:02 -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 48978 invoked by uid 99); 27 Oct 2017 07:26:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Oct 2017 07:26:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 857A21A17EA for ; Fri, 27 Oct 2017 07:26:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id obYY5N0aPmSh for ; Fri, 27 Oct 2017 07:26:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id E32605FB32 for ; Fri, 27 Oct 2017 07:26:00 +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 694D6E0373 for ; Fri, 27 Oct 2017 07:26:00 +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 22C5E212F5 for ; Fri, 27 Oct 2017 07:26:00 +0000 (UTC) Date: Fri, 27 Oct 2017 07:26:00 +0000 (UTC) From: "Vishal Khandelwal (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-19107) Backup should resume from last failed state MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 27 Oct 2017 07:26:09 -0000 Vishal Khandelwal created HBASE-19107: ----------------------------------------- Summary: Backup should resume from last failed state Key: HBASE-19107 URL: https://issues.apache.org/jira/browse/HBASE-19107 Project: HBase Issue Type: New Feature Environment: Consider that incremental backup is happenng for 10 tables for a set of 100 WALs. if backup @ 10th fails, then on net iteration it would be triggered again from 100 WALs + new WALs all tables This is a issue because resource and time used to do he backup of 9 table & 100 WALs are wasted Rather it should have functionality to resume from previous state complete that backup and then do new set of WALs. This will make it more performant Reporter: Vishal Khandelwal -- This message was sent by Atlassian JIRA (v6.4.14#64029)