[HDFS-3357] DataXceiver reads from client socket with incorrect/no timeout

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.0.2, 2.0.0-alpha
• Fix Version/s: 2.0.0-alpha
• Component/s: datanode
• Target Version/s: 2.0.0-alpha
• Hadoop Flags: Reviewed
• Assignee: Todd Lipcon
• Reporter: Todd Lipcon
• Created: 03/May/12 05:15
• Updated: 28/Sep/15 20:58
• Resolved: 04/May/12 18:51

Description

In DataXceiver, we currently use Socket.setSoTimeout to try to manage the read timeout when switching between reading the initial opCode, reading a keepalive opcode, and reading the status after a successfully sent block. However, since all of these reads use the same underlying DataInputStream, the change to the socket timeout isn't respected. Thus, they all occur with whatever timeout is set on the socket at the time of DataXceiver construction. In practice this turns out to be 0, which can cause infinitely hung xceivers.

Issue Links

• is blocked by: HADOOP-8350 Improve NetUtils.getInputStream to return a stream which has a tunable timeout