Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 11 May 2013 03:05:16 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12647149.1368241471026.304874.1368241516042@arcas>
In-Reply-To: <JIRA.12647149.1368241471026@arcas>
References: <JIRA.12647149.1368241471026@arcas>
Subject: [jira] [Created] (HBASE-8530) Refine error message from
 ExportSnapshot when there is leftover snapshot in target cluster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Ted Yu created HBASE-8530:
-----------------------------

             Summary: Refine error message from ExportSnapshot when there is leftover snapshot in target cluster
                 Key: HBASE-8530
                 URL: https://issues.apache.org/jira/browse/HBASE-8530
             Project: HBase
          Issue Type: Bug
            Reporter: Ted Yu
            Assignee: Ted Yu
            Priority: Minor


ExportSnapshot performs the following validation check before starting export:
{code}
    // Check if the snapshot already in-progress
    if (outputFs.exists(snapshotTmpDir)) {
      System.err.println("A snapshot with the same name '" + snapshotName + "' is in-progress");
      return 1;
    }
{code}
The intention was to prevent concurrent snapshot export when snapshot with the same name may be outstanding.
Here is sample output:
{code}
hbase@ip-10-165-36-226 root$ hbase org.apache.hadoop.hbase.snapshot.ExportSnapshot -snapshot snapone -copy-to hdfs://10.12.113.22:8020/apps/hbase/data -mappers 1
A snapshot with the same name 'snapone' is in-progress
{code}
We should note the actual path in the error message so that user can check whether the snapshot with same name is still pending.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira