[
https://issues.apache.org/jira/browse/HDFS-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461762#comment-13461762
]
Hadoop QA commented on HDFS-3878:
---------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12546282/HDFS-3878.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 2 new or modified test
files.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/3226//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3226//console
This message is automatically generated.
> Add an administrative command to download finalized edit log segments from
> the NN
> ---------------------------------------------------------------------------------
>
> Key: HDFS-3878
> URL: https://issues.apache.org/jira/browse/HDFS-3878
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: hdfs client, name-node
> Affects Versions: 2.0.0-alpha
> Reporter: Aaron T. Myers
> Labels: patch
> Attachments: HDFS-3878.patch, HDFS-3878.patch, HDFS-3878.patch,
> HDFS-3878.patch
>
>
> Similarly to the `hdfs dfsadmin -fetchImage' command added in HDFS-2941, it
> would be nice to have an admin command capable of fetching edit log segments.
> This could be useful, for example, for use in a script designed to back up
> the NN on-disk metadata.
--
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
