[
https://issues.apache.org/jira/browse/HADOOP-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681989#action_12681989
]
Hadoop QA commented on HADOOP-5464:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12401966/HADOOP-5464.patch
against trunk revision 753449.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
+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 Eclipse classpath. The patch retains Eclipse classpath integrity.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/65/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/65/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/65/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-minerva.apache.org/65/console
This message is automatically generated.
> DFSClient does not treat write timeout of 0 properly
> ----------------------------------------------------
>
> Key: HADOOP-5464
> URL: https://issues.apache.org/jira/browse/HADOOP-5464
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.17.0
> Reporter: Raghu Angadi
> Assignee: Raghu Angadi
> Attachments: HADOOP-5464.patch
>
>
> {{dfs.datanode.socket.write.timeout}} is used for sockets to and from
> datanodes. It is 8 minutes by default. Some users set this to 0, effectively
> disabling the write timeout (for some specific reasons).
> When this is set to 0, DFSClient sets the timeout to 5 seconds by mistake
> while writing to DataNodes. This is exactly the opposite of real intention of
> setting it to 0 since 5 seconds is too short.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
