[jira] [Commented] (HBASE-10537) Let the ExportSnapshot mapper fail and retry on error
[ https://issues.apache.org/jira/browse/HBASE-10537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13919396#comment-13919396 ] Hudson commented on HBASE-10537: FAILURE: Integrated in HBase-0.94-JDK7 #71 (See [https://builds.apache.org/job/HBase-0.94-JDK7/71/]) HBASE-10537 Let the ExportSnapshot mapper fail and retry on error (mbertozzi: rev 1574016) * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/snapshot/ExportSnapshot.java * /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/snapshot/TestExportSnapshot.java > Let the ExportSnapshot mapper fail and retry on error > - > > Key: HBASE-10537 > URL: https://issues.apache.org/jira/browse/HBASE-10537 > Project: HBase > Issue Type: Bug > Components: snapshots >Reporter: Matteo Bertozzi >Assignee: Matteo Bertozzi > Fix For: 0.96.2, 0.98.1, 0.99.0 > > Attachments: HBASE-10537-v1.patch, HBASE-10537-v2.patch > > > Instead of completing the job, and force the user to re-run the export if > something failed, let the Mapper fail and retry automatically based on the > job.getMaxMapAttempts() -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HBASE-10537) Let the ExportSnapshot mapper fail and retry on error
[ https://issues.apache.org/jira/browse/HBASE-10537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13919354#comment-13919354 ] Hudson commented on HBASE-10537: FAILURE: Integrated in HBase-0.94 #1307 (See [https://builds.apache.org/job/HBase-0.94/1307/]) HBASE-10537 Let the ExportSnapshot mapper fail and retry on error (mbertozzi: rev 1574016) * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/snapshot/ExportSnapshot.java * /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/snapshot/TestExportSnapshot.java > Let the ExportSnapshot mapper fail and retry on error > - > > Key: HBASE-10537 > URL: https://issues.apache.org/jira/browse/HBASE-10537 > Project: HBase > Issue Type: Bug > Components: snapshots >Reporter: Matteo Bertozzi >Assignee: Matteo Bertozzi > Fix For: 0.96.2, 0.98.1, 0.99.0 > > Attachments: HBASE-10537-v1.patch, HBASE-10537-v2.patch > > > Instead of completing the job, and force the user to re-run the export if > something failed, let the Mapper fail and retry automatically based on the > job.getMaxMapAttempts() -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HBASE-10537) Let the ExportSnapshot mapper fail and retry on error
[ https://issues.apache.org/jira/browse/HBASE-10537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13919300#comment-13919300 ] Hudson commented on HBASE-10537: FAILURE: Integrated in HBase-0.94-on-Hadoop-2 #38 (See [https://builds.apache.org/job/HBase-0.94-on-Hadoop-2/38/]) HBASE-10537 Let the ExportSnapshot mapper fail and retry on error (mbertozzi: rev 1574016) * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/snapshot/ExportSnapshot.java * /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/snapshot/TestExportSnapshot.java > Let the ExportSnapshot mapper fail and retry on error > - > > Key: HBASE-10537 > URL: https://issues.apache.org/jira/browse/HBASE-10537 > Project: HBase > Issue Type: Bug > Components: snapshots >Reporter: Matteo Bertozzi >Assignee: Matteo Bertozzi > Fix For: 0.96.2, 0.98.1, 0.99.0 > > Attachments: HBASE-10537-v1.patch, HBASE-10537-v2.patch > > > Instead of completing the job, and force the user to re-run the export if > something failed, let the Mapper fail and retry automatically based on the > job.getMaxMapAttempts() -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HBASE-10537) Let the ExportSnapshot mapper fail and retry on error
[ https://issues.apache.org/jira/browse/HBASE-10537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13919276#comment-13919276 ] Hudson commented on HBASE-10537: FAILURE: Integrated in HBase-0.94-security #428 (See [https://builds.apache.org/job/HBase-0.94-security/428/]) HBASE-10537 Let the ExportSnapshot mapper fail and retry on error (mbertozzi: rev 1574016) * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/snapshot/ExportSnapshot.java * /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/snapshot/TestExportSnapshot.java > Let the ExportSnapshot mapper fail and retry on error > - > > Key: HBASE-10537 > URL: https://issues.apache.org/jira/browse/HBASE-10537 > Project: HBase > Issue Type: Bug > Components: snapshots >Reporter: Matteo Bertozzi >Assignee: Matteo Bertozzi > Fix For: 0.96.2, 0.98.1, 0.99.0 > > Attachments: HBASE-10537-v1.patch, HBASE-10537-v2.patch > > > Instead of completing the job, and force the user to re-run the export if > something failed, let the Mapper fail and retry automatically based on the > job.getMaxMapAttempts() -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HBASE-10537) Let the ExportSnapshot mapper fail and retry on error
[ https://issues.apache.org/jira/browse/HBASE-10537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906380#comment-13906380 ] Hudson commented on HBASE-10537: FAILURE: Integrated in HBase-TRUNK-on-Hadoop-1.1 #94 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-1.1/94/]) HBASE-10537 Let the ExportSnapshot mapper fail and retry on error (mbertozzi: rev 1569680) * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/snapshot/ExportSnapshot.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/TestExportSnapshot.java > Let the ExportSnapshot mapper fail and retry on error > - > > Key: HBASE-10537 > URL: https://issues.apache.org/jira/browse/HBASE-10537 > Project: HBase > Issue Type: Bug > Components: snapshots >Reporter: Matteo Bertozzi >Assignee: Matteo Bertozzi > Fix For: 0.96.2, 0.98.1, 0.99.0 > > Attachments: HBASE-10537-v1.patch, HBASE-10537-v2.patch > > > Instead of completing the job, and force the user to re-run the export if > something failed, let the Mapper fail and retry automatically based on the > job.getMaxMapAttempts() -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (HBASE-10537) Let the ExportSnapshot mapper fail and retry on error
[ https://issues.apache.org/jira/browse/HBASE-10537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13905493#comment-13905493 ] Hudson commented on HBASE-10537: SUCCESS: Integrated in HBase-0.98 #168 (See [https://builds.apache.org/job/HBase-0.98/168/]) HBASE-10537 Let the ExportSnapshot mapper fail and retry on error (mbertozzi: rev 1569682) * /hbase/branches/0.98/hbase-server/src/main/java/org/apache/hadoop/hbase/snapshot/ExportSnapshot.java * /hbase/branches/0.98/hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/TestExportSnapshot.java > Let the ExportSnapshot mapper fail and retry on error > - > > Key: HBASE-10537 > URL: https://issues.apache.org/jira/browse/HBASE-10537 > Project: HBase > Issue Type: Bug > Components: snapshots >Reporter: Matteo Bertozzi >Assignee: Matteo Bertozzi > Fix For: 0.96.2, 0.98.1, 0.99.0 > > Attachments: HBASE-10537-v1.patch, HBASE-10537-v2.patch > > > Instead of completing the job, and force the user to re-run the export if > something failed, let the Mapper fail and retry automatically based on the > job.getMaxMapAttempts() -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (HBASE-10537) Let the ExportSnapshot mapper fail and retry on error
[ https://issues.apache.org/jira/browse/HBASE-10537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13905463#comment-13905463 ] Hudson commented on HBASE-10537: SUCCESS: Integrated in hbase-0.96 #302 (See [https://builds.apache.org/job/hbase-0.96/302/]) HBASE-10537 Let the ExportSnapshot mapper fail and retry on error (mbertozzi: rev 1569686) * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/snapshot/ExportSnapshot.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/TestExportSnapshot.java > Let the ExportSnapshot mapper fail and retry on error > - > > Key: HBASE-10537 > URL: https://issues.apache.org/jira/browse/HBASE-10537 > Project: HBase > Issue Type: Bug > Components: snapshots >Reporter: Matteo Bertozzi >Assignee: Matteo Bertozzi > Fix For: 0.96.2, 0.98.1, 0.99.0 > > Attachments: HBASE-10537-v1.patch, HBASE-10537-v2.patch > > > Instead of completing the job, and force the user to re-run the export if > something failed, let the Mapper fail and retry automatically based on the > job.getMaxMapAttempts() -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (HBASE-10537) Let the ExportSnapshot mapper fail and retry on error
[ https://issues.apache.org/jira/browse/HBASE-10537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13905425#comment-13905425 ] Hudson commented on HBASE-10537: SUCCESS: Integrated in HBase-0.98-on-Hadoop-1.1 #157 (See [https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/157/]) HBASE-10537 Let the ExportSnapshot mapper fail and retry on error (mbertozzi: rev 1569682) * /hbase/branches/0.98/hbase-server/src/main/java/org/apache/hadoop/hbase/snapshot/ExportSnapshot.java * /hbase/branches/0.98/hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/TestExportSnapshot.java > Let the ExportSnapshot mapper fail and retry on error > - > > Key: HBASE-10537 > URL: https://issues.apache.org/jira/browse/HBASE-10537 > Project: HBase > Issue Type: Bug > Components: snapshots >Reporter: Matteo Bertozzi >Assignee: Matteo Bertozzi > Fix For: 0.96.2, 0.98.1, 0.99.0 > > Attachments: HBASE-10537-v1.patch, HBASE-10537-v2.patch > > > Instead of completing the job, and force the user to re-run the export if > something failed, let the Mapper fail and retry automatically based on the > job.getMaxMapAttempts() -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (HBASE-10537) Let the ExportSnapshot mapper fail and retry on error
[ https://issues.apache.org/jira/browse/HBASE-10537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13905400#comment-13905400 ] Hudson commented on HBASE-10537: FAILURE: Integrated in hbase-0.96-hadoop2 #208 (See [https://builds.apache.org/job/hbase-0.96-hadoop2/208/]) HBASE-10537 Let the ExportSnapshot mapper fail and retry on error (mbertozzi: rev 1569686) * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/snapshot/ExportSnapshot.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/TestExportSnapshot.java > Let the ExportSnapshot mapper fail and retry on error > - > > Key: HBASE-10537 > URL: https://issues.apache.org/jira/browse/HBASE-10537 > Project: HBase > Issue Type: Bug > Components: snapshots >Reporter: Matteo Bertozzi >Assignee: Matteo Bertozzi > Fix For: 0.96.2, 0.98.1, 0.99.0 > > Attachments: HBASE-10537-v1.patch, HBASE-10537-v2.patch > > > Instead of completing the job, and force the user to re-run the export if > something failed, let the Mapper fail and retry automatically based on the > job.getMaxMapAttempts() -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (HBASE-10537) Let the ExportSnapshot mapper fail and retry on error
[ https://issues.apache.org/jira/browse/HBASE-10537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13905394#comment-13905394 ] Hudson commented on HBASE-10537: SUCCESS: Integrated in HBase-TRUNK #4931 (See [https://builds.apache.org/job/HBase-TRUNK/4931/]) HBASE-10537 Let the ExportSnapshot mapper fail and retry on error (mbertozzi: rev 1569680) * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/snapshot/ExportSnapshot.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/TestExportSnapshot.java > Let the ExportSnapshot mapper fail and retry on error > - > > Key: HBASE-10537 > URL: https://issues.apache.org/jira/browse/HBASE-10537 > Project: HBase > Issue Type: Bug > Components: snapshots >Reporter: Matteo Bertozzi >Assignee: Matteo Bertozzi > Fix For: 0.96.2, 0.98.1, 0.99.0 > > Attachments: HBASE-10537-v1.patch, HBASE-10537-v2.patch > > > Instead of completing the job, and force the user to re-run the export if > something failed, let the Mapper fail and retry automatically based on the > job.getMaxMapAttempts() -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (HBASE-10537) Let the ExportSnapshot mapper fail and retry on error
[ https://issues.apache.org/jira/browse/HBASE-10537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904688#comment-13904688 ] Jonathan Hsieh commented on HBASE-10537: +1, lgtm. > Let the ExportSnapshot mapper fail and retry on error > - > > Key: HBASE-10537 > URL: https://issues.apache.org/jira/browse/HBASE-10537 > Project: HBase > Issue Type: Bug > Components: snapshots >Reporter: Matteo Bertozzi >Assignee: Matteo Bertozzi > Fix For: 0.98.1, 0.99.0 > > Attachments: HBASE-10537-v1.patch, HBASE-10537-v2.patch > > > Instead of completing the job, and force the user to re-run the export if > something failed, let the Mapper fail and retry automatically based on the > job.getMaxMapAttempts() -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (HBASE-10537) Let the ExportSnapshot mapper fail and retry on error
[
https://issues.apache.org/jira/browse/HBASE-10537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904681#comment-13904681
]
Hadoop QA commented on HBASE-10537:
---
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12629615/HBASE-10537-v2.patch
against trunk revision .
ATTACHMENT ID: 12629615
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop1.1{color}. The patch compiles against the hadoop
1.1 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/8737//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8737//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8737//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8737//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8737//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8737//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8737//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8737//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8737//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8737//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/8737//console
This message is automatically generated.
> Let the ExportSnapshot mapper fail and retry on error
> -
>
> Key: HBASE-10537
> URL: https://issues.apache.org/jira/browse/HBASE-10537
> Project: HBase
> Issue Type: Bug
> Components: snapshots
>Reporter: Matteo Bertozzi
>Assignee: Matteo Bertozzi
> Fix For: 0.98.1, 0.99.0
>
> Attachments: HBASE-10537-v1.patch, HBASE-10537-v2.patch
>
>
> Instead of completing the job, and force the user to re-run the export if
> something failed, let the Mapper fail and retry automatically based on the
> job.getMaxMapAttempts()
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (HBASE-10537) Let the ExportSnapshot mapper fail and retry on error
[
https://issues.apache.org/jira/browse/HBASE-10537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904093#comment-13904093
]
Jonathan Hsieh commented on HBASE-10537:
Looks good once qabot gets satsified.
nit: rename to injectTestFailure or simulateTestFailure?
{code}
+ private void testFailure(final Context context, final Path inputPath)
+throws IOException {
+
{code}
> Let the ExportSnapshot mapper fail and retry on error
> -
>
> Key: HBASE-10537
> URL: https://issues.apache.org/jira/browse/HBASE-10537
> Project: HBase
> Issue Type: Bug
> Components: snapshots
>Reporter: Matteo Bertozzi
>Assignee: Matteo Bertozzi
> Fix For: 0.98.1, 0.99.0
>
> Attachments: HBASE-10537-v1.patch
>
>
> Instead of completing the job, and force the user to re-run the export if
> something failed, let the Mapper fail and retry automatically based on the
> job.getMaxMapAttempts()
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (HBASE-10537) Let the ExportSnapshot mapper fail and retry on error
[
https://issues.apache.org/jira/browse/HBASE-10537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901713#comment-13901713
]
Hadoop QA commented on HBASE-10537:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12629036/HBASE-10537-v1.patch
against trunk revision .
ATTACHMENT ID: 12629036
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop1.1{color}. The patch compiles against the hadoop
1.1 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:red}-1 site{color}. The patch appears to cause mvn site goal to
fail.
{color:red}-1 core tests{color}. The patch failed these unit tests:
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
at
org.apache.hadoop.hbase.regionserver.wal.TestLogRolling.testLogRollOnDatanodeDeath(TestLogRolling.java:354)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/8705//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8705//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8705//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8705//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8705//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8705//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8705//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8705//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8705//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8705//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/8705//console
This message is automatically generated.
> Let the ExportSnapshot mapper fail and retry on error
> -
>
> Key: HBASE-10537
> URL: https://issues.apache.org/jira/browse/HBASE-10537
> Project: HBase
> Issue Type: Bug
> Components: snapshots
>Reporter: Matteo Bertozzi
>Assignee: Matteo Bertozzi
> Fix For: 0.98.0, 0.99.0
>
> Attachments: HBASE-10537-v1.patch
>
>
> Instead of completing the job, and force the user to re-run the export if
> something failed, let the Mapper fail and retry automatically based on the
> job.getMaxMapAttempts()
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Commented] (HBASE-10537) Let the ExportSnapshot mapper fail and retry on error
[
https://issues.apache.org/jira/browse/HBASE-10537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901523#comment-13901523
]
Hadoop QA commented on HBASE-10537:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12629015/HBASE-10537-v0.patch
against trunk revision .
ATTACHMENT ID: 12629015
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:red}-1 hadoop1.0{color}. The patch failed to compile against the
hadoop 1.0 profile.
Here is snippet of errors:
{code}[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile)
on project hbase-server: Compilation failure: Compilation failure:
[ERROR]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/snapshot/ExportSnapshot.java:[568,41]
cannot find symbol
[ERROR] symbol : method getMaxMapAttempts()
[ERROR] location: class org.apache.hadoop.mapreduce.Job
[ERROR]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/snapshot/ExportSnapshot.java:[575,14]
cannot find symbol
[ERROR] symbol : method monitorAndPrintJob()
--
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile)
on project hbase-server: Compilation failure
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
--
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation
failure
at
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:729)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more{code}
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/8702//console
This message is automatically generated.
> Let the ExportSnapshot mapper fail and retry on error
> -
>
> Key: HBASE-10537
> URL: https://issues.apache.org/jira/browse/HBASE-10537
> Project: HBase
> Issue Type: Bug
> Components: snapshots
>Reporter: Matteo Bertozzi
>Assignee: Matteo Bertozzi
> Fix For: 0.98.0, 0.99.0
>
> Attachments: HBASE-10537-v0.patch
>
>
> Instead of completing the job, and force the user to re-run the export if
> something failed, let the Mapper fail and retry automatically based on the
> job.getMaxMapAttempts()
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
