[HDFS-1075] Separately configure connect timeouts from read timeouts in data path

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: datanode, hdfs-client
• Assignee: Unassigned
• Reporter: Todd Lipcon
• Created: 02/Apr/10 17:12
• Updated: 15/Aug/12 08:40

Description

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.

Issue Links

• is related to: HDFS-770 SocketTimeoutException: timeout while waiting for channel to be ready for read
• relates to: HBASE-5843 Improve HBase MTTR - Mean Time To Recover