[
https://issues.apache.org/jira/browse/HDFS-13735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575184#comment-16575184
]
Hudson commented on HDFS-13735:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14740 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/14740/])
HDFS-13735. Make QJM HTTP URL connection timeout configurable. (cliang: rev
5326a7906de7c86a236d948012cabf3a9ba82310)
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSConfigKeys.java
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/qjournal/client/QuorumJournalManager.java
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/main/resources/hdfs-default.xml
> Make QJM HTTP URL connection timeout configurable
> -------------------------------------------------
>
> Key: HDFS-13735
> URL: https://issues.apache.org/jira/browse/HDFS-13735
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: qjm
> Reporter: Chao Sun
> Assignee: Chao Sun
> Priority: Minor
> Fix For: 3.2.0, 3.1.2
>
> Attachments: HDFS-13735.000.patch, HDFS-13735.001.patch
>
>
> We've seen "connect timed out" happen internally when QJM tries to open HTTP
> connections to JNs. This is now using {{newDefaultURLConnectionFactory}}
> which uses the default timeout 60s, and is not configurable.
> It would be better for this to be configurable, especially for
> ObserverNameNode (HDFS-12943), where latency is important, and 60s may not be
> a good value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
