[
https://issues.apache.org/jira/browse/HDFS-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434882#comment-13434882
]
nkeywal commented on HDFS-1075:
-------------------------------
This could be very useful. The connect is not impacted by stuff like garbage
collection; so if the node is still alive, it will reply to the connect quickly.
> Separately configure connect timeouts from read timeouts in data path
> ---------------------------------------------------------------------
>
> Key: HDFS-1075
> URL: https://issues.apache.org/jira/browse/HDFS-1075
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: data-node, hdfs client
> Reporter: Todd Lipcon
>
> The timeout configurations in the write pipeline overload the read timeout to
> also include a connect timeout. In my experience, if a node is down it can
> take many seconds to get back an exception connect, whereas if it is up it
> will accept almost immediately, even if heavily loaded (the kernel listen
> backlog picks it up very fast). So in the interest of faster dead node
> detection from the writer perspective, the connect timeout should be
> configured separately, usually to a much lower time than the read timeout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
