[
https://issues.apache.org/jira/browse/HDFS-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730122#action_12730122
]
Hadoop QA commented on HDFS-278:
--------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12413239/softMount9.txt
against trunk revision 793365.
+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 warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-vesta.apache.org/18/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-vesta.apache.org/18/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-vesta.apache.org/18/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-vesta.apache.org/18/console
This message is automatically generated.
> Should DFS outputstream's close wait forever?
> ---------------------------------------------
>
> Key: HDFS-278
> URL: https://issues.apache.org/jira/browse/HDFS-278
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Raghu Angadi
> Assignee: dhruba borthakur
> Fix For: 0.21.0
>
> Attachments: softMount1.patch, softMount1.patch, softMount2.patch,
> softMount3.patch, softMount4.txt, softMount5.txt, softMount6.txt,
> softMount7.txt, softMount8.txt, softMount9.txt
>
>
> Currently {{DFSOutputStream.close()}} waits for ever if Namenode keeps
> throwing {{NotYetReplicated}} exception, for whatever reason. Its pretty
> annoying for a user. Shoud the loop inside close have a timeout? If so how
> much? It could probably something like 10 minutes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
