[HADOOP-317] "connection was forcibly closed" Exception in RPC on Windows

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.3.2
• Fix Version/s: 0.4.0
• Component/s: ipc
• Assignee: Doug Cutting
• Reporter: Konstantin Shvachko
• Created: 23/Jun/06 01:51
• Updated: 03/Aug/06 17:46
• Resolved: 23/Jun/06 04:06

Description

I see a lot of exceptions caused by RPC in the nightly build on Windows.
The most often is thrown by RPC on the namenode, saying

06/06/21 19:28:36 INFO ipc.Server: Server listener on port 7017: readAndProcess threw exception java.io.IOException: An existing connection was forcibly closed by the remote host. Count of bytes read: 0
java.io.IOException: An existing connection was forcibly closed by the remote host
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:25)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:233)
at sun.nio.ch.IOUtil.read(IOUtil.java:200)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:207)
at org.apache.hadoop.ipc.Server$Connection.readAndProcess(Server.java:374)
at org.apache.hadoop.ipc.Server$Listener.doRead(Server.java:289)
at org.apache.hadoop.ipc.Server$Listener.run(Server.java:210)

I am not sure how serious that is, since the tests do not fail, and the name node does not crash.
Besides the RPC we should probably also check that the unit tests actually fail if they need to.