Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.3.1
-
None
-
None
Description
In my sort benchmark, I've started seeing hundred's of maps dying with timeout exceptions in the dfs.open() code:
java.net.SocketTimeoutException: timed out waiting for rpc response at org.apache.hadoop.ipc.Client.call(Client.java:305) at org.apache.hadoop.ipc.RPC$Invoker.invoke(RPC.java:153) at org.apache.hadoop.dfs.$Proxy1.open(Unknown Source) at org.apache.hadoop.dfs.DFSClient$DFSInputStream.openInfo(DFSClient.java:457) at org.apache.hadoop.dfs.DFSClient$DFSInputStream.(DFSClient.java:444) at org.apache.hadoop.dfs.DFSClient.open(DFSClient.java:207) at org.apache.hadoop.dfs.DistributedFileSystem.openRaw(DistributedFileSystem.java:90) at org.apache.hadoop.fs.FSDataInputStream$Checker.(FSDataInputStream.java:46) at org.apache.hadoop.fs.FSDataInputStream.(FSDataInputStream.java:228) at org.apache.hadoop.fs.FileSystem.open(FileSystem.java:157) at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:72) at org.apache.hadoop.dfs.DistributedFileSystem.copyToLocalFile(DistributedFileSystem.java:182) at org.apache.hadoop.mapred.TaskTracker$TaskInProgress.localizeTask(TaskTracker.java:535) at org.apache.hadoop.mapred.TaskTracker$TaskInProgress.launchTask(TaskTracker.java:584) at org.apache.hadoop.mapred.TaskTracker.startNewTask(TaskTracker.java:395) at org.apache.hadoop.mapred.TaskTracker.offerService(TaskTracker.java:308) at org.apache.hadoop.mapred.TaskTracker.run(TaskTracker.java:424) at org.apache.hadoop.mapred.TaskTracker.main(TaskTracker.java:961)