[
https://issues.apache.org/jira/browse/HDFS-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974077#action_12974077
]
Hadoop QA commented on HDFS-1509:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12466375/resyncBadNameDir3.txt
against trunk revision 1051669.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+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 failed these core unit tests:
org.apache.hadoop.hdfs.server.namenode.TestStorageRestore
org.apache.hadoop.hdfs.TestFileConcurrentReader
org.apache.hadoop.hdfs.TestHDFSTrash
-1 contrib tests. The patch failed contrib unit tests.
+1 system test framework. The patch passed system test framework compile.
Test results:
https://hudson.apache.org/hudson/job/PreCommit-HDFS-Build/38//testReport/
Findbugs warnings:
https://hudson.apache.org/hudson/job/PreCommit-HDFS-Build/38//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://hudson.apache.org/hudson/job/PreCommit-HDFS-Build/38//console
This message is automatically generated.
> Resync discarded directories in fs.name.dir during saveNamespace command
> ------------------------------------------------------------------------
>
> Key: HDFS-1509
> URL: https://issues.apache.org/jira/browse/HDFS-1509
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: name-node
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Attachments: resyncBadNameDir1.txt, resyncBadNameDir2.txt,
> resyncBadNameDir3.txt
>
>
> In the current implementation, if the Namenode encounters an error while
> writing to a fs.name.dir directory it stops writing new edits to that
> directory. My proposal is to make the namenode write the fsimage to all
> configured directories in fs.name.dir, and from then on, continue writing
> fsedits to all configured directories.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
