[
https://issues.apache.org/jira/browse/HADOOP-7397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050682#comment-13050682
]
Hadoop QA commented on HADOOP-7397:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12482821/timeout.patch
against trunk revision 1136249.
+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 new tests are needed for this
patch.
Also please list what manual steps were performed to
verify 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 (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 core unit tests.
+1 system test framework. The patch passed system test framework compile.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/642//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HADOOP-Build/642//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/642//console
This message is automatically generated.
> Allow configurable timeouts when connecting to HDFS via java FileSystem API
> ---------------------------------------------------------------------------
>
> Key: HADOOP-7397
> URL: https://issues.apache.org/jira/browse/HADOOP-7397
> Project: Hadoop Common
> Issue Type: Improvement
> Components: ipc
> Affects Versions: 0.20.2, 0.23.0
> Environment: Any
> Reporter: Scott Fines
> Priority: Minor
> Labels: hadoop
> Fix For: 0.23.0
>
> Attachments: timeout.patch
>
>
> If the NameNode is not available (in, for example, a network partition event
> separating the client from the NameNode), and an attempt is made to connect,
> then the FileSystem api will *eventually* timeout and throw an error.
> However, that timeout is currently hardcoded to be 20 seconds to connect,
> with 45 retries, for a total of a 15 minute wait before failure. While in
> many circumstances this is fine, there are also many circumstances (such as
> booting a service) where both the connection timeout and the number of
> retries should be significantly less, so as not to harm availability of other
> services.
> Investigating Client.java, I see that there are two fields in Connection:
> maxRetries and rpcTimeout. I propose either re-using those fields for
> initiating the connection as well; alternatively, using the already existing
> dfs.socket.timeout parameter to set the connection timeout on initialization,
> and potentially adding a new field such as dfs.connection.retries with a
> default of 45 to replicate current behaviors.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
