[HADOOP-5464] DFSClient does not treat write timeout of 0 properly

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.17.0
• Fix Version/s: 1.1.0, 0.21.0
• Hadoop Flags: Incompatible change, Reviewed
• Release Note: Zero values for dfs.socket.timeout and dfs.datanode.socket.write.timeout are now respected. Previously zero values for these parameters resulted in a 5 second timeout.
• Assignee: Raghu Angadi
• Reporter: Raghu Angadi
• Created: 11/Mar/09 20:11
• Updated: 29/May/12 21:19
• Resolved: 31/Mar/09 19:40

Description

dfs.datanode.socket.write.timeout is used for sockets to and from datanodes. It is 8 minutes by default. Some users set this to 0, effectively disabling the write timeout (for some specific reasons).

When this is set to 0, DFSClient sets the timeout to 5 seconds by mistake while writing to DataNodes. This is exactly the opposite of real intention of setting it to 0 since 5 seconds is too short.