[HADOOP-2971] SocketTimeoutException in unit tests

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.17.0
• Fix Version/s: 0.17.0
• Component/s: io
• Assignee: Raghu Angadi
• Reporter: Raghu Angadi
• Created: 07/Mar/08 21:42
• Updated: 21/May/08 20:05
• Resolved: 11/Mar/08 03:51

Description

TestJobStatusPersistency failed and contained DataNode stacktraces similar to the following :

2008-03-07 21:27:00,410 ERROR dfs.DataNode (DataNode.java:run(976)) - 127.0.0.1:57790:DataXceiver: java.net.SocketTimeoutException: 0 millis 
timeout while waiting for Unknown Addr (local: /127.0.0.1:57790) to be ready for read
        at org.apache.hadoop.net.SocketIOWithTimeout.doIO(SocketIOWithTimeout.java:188)
        at org.apache.hadoop.net.SocketInputStream.read(SocketInputStream.java:135)
        at org.apache.hadoop.net.SocketInputStream.read(SocketInputStream.java:121)
        at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
        at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
        at java.io.DataInputStream.readInt(DataInputStream.java:370)
        at org.apache.hadoop.dfs.DataNode$BlockReceiver.receiveBlock(DataNode.java:2434)
        at org.apache.hadoop.dfs.DataNode$DataXceiver.writeBlock(DataNode.java:1170)
        at org.apache.hadoop.dfs.DataNode$DataXceiver.run(DataNode.java:953)
        at java.lang.Thread.run(Thread.java:619)

This is mostly related to HADOOP-2346. The error is strange. socket.getRemoteSocketAddress() returned null implying this socket is not connected yet. But we have already read a few bytes from it!.