[HADOOP-8350] Improve NetUtils.getInputStream to return a stream which has a tunable timeout

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0, 2.0.0-alpha
• Fix Version/s: 2.0.0-alpha
• Component/s: util
• Target Version/s: 2.0.0-alpha
• Hadoop Flags: Reviewed
• Assignee: Todd Lipcon
• Reporter: Todd Lipcon
• Created: 03/May/12 05:17
• Updated: 14/Jul/12 23:33
• Resolved: 03/May/12 21:59

Description

Currently, NetUtils.getInputStream will set the timeout on the new stream based on the socket's configured timeout at the time of construction. After that, the timeout cannot be changed. This causes a problem for cases like HDFS-3357. One approach used in some places in the code is to construct new streams when the timeout has to be changed, but this can cause bugs given that the streams are often wrapped by BufferedInputStreams.

Issue Links

• blocks: HDFS-3357 DataXceiver reads from client socket with incorrect/no timeout
• relates to: HBASE-6396 Fix NoSuchMethodError running against hadoop 2.0