[
https://issues.apache.org/jira/browse/HDFS-12544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16219923#comment-16219923
]
Manoj Govindassamy commented on HDFS-12544:
-------------------------------------------
The build failure doesn't look related to the commit.
{noformat}
[INFO] Apache Hadoop Cloud Storage Project ................ FAILURE [ 3.193 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 17:45 min
[INFO] Finished at: 2017-10-26T01:22:04+00:00
[INFO] Final Memory: 440M/4669M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy (default-deploy) on
project hadoop-cloud-storage-project: Failed to retrieve remote metadata
org.apache.hadoop:hadoop-main:3.1.0-SNAPSHOT/maven-metadata.xml: Could not
transfer metadata
org.apache.hadoop:hadoop-main:3.1.0-SNAPSHOT/maven-metadata.xml from/to
apache.snapshots.https
(https://repository.apache.org/content/repositories/snapshots): Failed to
transfer file:
https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/hadoop-main/3.1.0-SNAPSHOT/maven-metadata.xml.
Return code is: 503 , ReasonPhrase:Service Unavailable. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :hadoop-cloud-storage-project
Build step 'Execute shell' marked build as failure
[JIRA] Updating issue HDFS-12544
[JIRA] Updating issue HADOOP-14957
[JIRA] Updating issue HDFS-12579
[JIRA] Updating issue YARN-4827
[JIRA] Updating issue HADOOP-14840
ERROR: No tool found matching LATEST1_8_HOME
Setting MAVEN_3_3_3_HOME=/home/jenkins/tools/maven/apache-maven-3.3.3
Finished: FAILURE
{noformat}
> SnapshotDiff - support diff generation on any snapshot root descendant
> directory
> --------------------------------------------------------------------------------
>
> Key: HDFS-12544
> URL: https://issues.apache.org/jira/browse/HDFS-12544
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
> Affects Versions: 3.0.0-beta1
> Reporter: Manoj Govindassamy
> Assignee: Manoj Govindassamy
> Fix For: 3.0.0
>
> Attachments: HDFS-12544.01.patch, HDFS-12544.02.patch,
> HDFS-12544.03.patch, HDFS-12544.04.patch, HDFS-12544.05.patch
>
>
> {noformat}
> # hdfs snapshotDiff <snapshot_root_path> <from_snapshot_name>
> <to_snapshot_name>
> {noformat}
> Using snapshot diff command, we can generate a diff report between any two
> given snapshots under a snapshot root directory. The command today only
> accepts the path that is a snapshot root. There are many deployments where
> the snapshot root is configured at the higher level directory but the diff
> report needed is only for a specific directory under the snapshot root. In
> these cases, the diff report can be filtered for changes pertaining to the
> directory we are interested in. But when the snapshot root directory is very
> huge, the snapshot diff report generation can take minutes even if we are
> interested to know the changes only in a small directory. So, it would be
> highly performant if the diff report calculation can be limited to only the
> interesting sub-directory of the snapshot root instead of the whole snapshot
> root.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
