Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 23 Jun 2016 00:40:16 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12982111.1466631776000.4237.1466642416191@Atlassian.JIRA>
In-Reply-To: <JIRA.12982111.1466631776000@Atlassian.JIRA>
References: <JIRA.12982111.1466631776000@Atlassian.JIRA> <JIRA.12982111.1466631776035@arcas>
Subject: [jira] [Updated] (HBASE-16088) hbase restore gives a misleading
 message if the table doesn't exist
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 23 Jun 2016 00:40:18 -0000


     [ https://issues.apache.org/jira/browse/HBASE-16088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ted Yu updated HBASE-16088:
---------------------------
    Attachment: 16088.v2.txt

In patch v2, I dropped table name since table name is not involved for the second manifestPath.

> hbase restore gives a misleading message if the table doesn't exist
> -------------------------------------------------------------------
>
>                 Key: HBASE-16088
>                 URL: https://issues.apache.org/jira/browse/HBASE-16088
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>            Priority: Minor
>              Labels: backup
>         Attachments: 16088.v1.txt, 16088.v2.txt
>
>
> [~cartershanklin] reported the following:
> This backup path and ID exist. When an existing table name is used:
> {code}
> [vagrant@hdp250-hbase ~]$ sudo -u hbase hbase restore /tmp/backup_incremental $FULL_BACKUP_ID TEST_DATA
> 2016-05-10 18:05:22,380 ERROR [main] impl.RestoreClientImpl: Existing table found in the restore target, please add "-overwrite" option in the command if you mean to restore to these existing tables
> 2016-05-10 18:05:22,380 INFO  [main] impl.RestoreClientImpl: Existing table list in restore target: [TEST_DATA]
> 2016-05-10 18:05:22,380 ERROR [main] impl.RestoreClientImpl: ERROR: restore failed with error: Existing table found in target while no "-overwrite" option found
> java.io.IOException: Existing table found in target while no "-overwrite" option found
> {code}
> If I use a table name that doesn't exist I get this:
> {code}
> [vagrant@hdp250-hbase ~]$ sudo -u hbase hbase restore /tmp/backup_incremental $FULL_BACKUP_ID fda
> java.io.IOException: Could not find backup manifest for backup_1462900212093 in /tmp/backup_incremental
> {code}
> The error message suggests there is some manifest file under /tmp/backup_incremental/backup_1462900212093 and that probably this directory backup_1462900212093 doesn't exist. Looking at the code, it is actually drilling down into a table at this point which is not obvious to me.
> If the message said something like "could not find backup manifest (.backup.manifest) for table X within /base/path" I think this would be a lot easier to diagnose.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)