[
https://issues.apache.org/jira/browse/HDFS-13735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554951#comment-16554951
]
Konstantin Shvachko commented on HDFS-13735:
--------------------------------------------
Looked at your patch, Chao. I am not a big fan of adding new timeout
configuration parameters for every type of connection. QJM and Hadoop in
general have already a bunch of those. So my questions are:
# Can we reuse an existing parameter for this purpose?
# If we cannot use existing, should we make the new ones public, keep
undocumented, or use a reasonable hard-coded constant?
# If we introduce a new parameter, we should give it a reasonable default
value. What is the reasonable timeout here? You set it to the old default.
# The best solution would be to take the http call ({{readOp()}}) out of the
global lock. Can it be done?
> 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
> 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]
