Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Fri, 12 Aug 2016 18:16:20 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12997013.1471025750000.294913.1471025780555@Atlassian.JIRA>
In-Reply-To: <JIRA.12997013.1471025750000@Atlassian.JIRA>
References: <JIRA.12997013.1471025750000@Atlassian.JIRA> <JIRA.12997013.1471025750566@arcas>
Subject: [jira] [Created] (HBASE-16410) Retry distcp job when previous
 distcp job didn't succeed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 12 Aug 2016 18:16:22 -0000

Ted Yu created HBASE-16410:
------------------------------

             Summary: Retry distcp job when previous distcp job didn't succeed
                 Key: HBASE-16410
                 URL: https://issues.apache.org/jira/browse/HBASE-16410
             Project: HBase
          Issue Type: Improvement
            Reporter: Ted Yu
            Assignee: Ted Yu


Currently when copyService.copy() returns non-zero return value, we throw exception:
{code}
        throw new IOException("Failed of Hadoop Distributed Copy from "+
            StringUtils.join(incrBackupFileList, ",") +" to "
          + backupContext.getHLogTargetDir());
{code}
We should retry distcp job when the return value is non-zero instead of throwing IOException immediately.


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