[
https://issues.apache.org/jira/browse/MAPREDUCE-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791974#action_12791974
]
Brian Karlak commented on MAPREDUCE-1308:
-----------------------------------------
And I see one message for a SocketTimeout:
2009-12-17 06:26:20,082 WARN org.apache.hadoop.hdfs.server.datanode.DataNode:
DatanodeRegistration(172.29.2.67:50010,
storageID=DS-739735928-172.29.2.67-50010-1259798617913, infoPort=50075,
ipcPort=50020):Got exception while serving blk_-7712543153225807619_1300911 to
/172.29.2.67:
java.net.SocketTimeoutException: 480000 millis timeout while waiting for
channel to be ready for write. ch : java.nio.channels.SocketChannel[connected
local=/172.29.2.67:50010 remote=/172.29.2.67:41058]
at
org.apache.hadoop.net.SocketIOWithTimeout.waitForIO(SocketIOWithTimeout.java:185)
at
org.apache.hadoop.net.SocketOutputStream.waitForWritable(SocketOutputStream.java:159)
at
org.apache.hadoop.net.SocketOutputStream.transferToFully(SocketOutputStream.java:198)
at
org.apache.hadoop.hdfs.server.datanode.BlockSender.sendChunks(BlockSender.java:313)
at
org.apache.hadoop.hdfs.server.datanode.BlockSender.sendBlock(BlockSender.java:400)
at
org.apache.hadoop.hdfs.server.datanode.DataXceiver.readBlock(DataXceiver.java:180)
at
org.apache.hadoop.hdfs.server.datanode.DataXceiver.run(DataXceiver.java:95)
at java.lang.Thread.run(Thread.java:619)
2009-12-17 06:26:20,082 ERROR org.apache.hadoop.hdfs.server.datanode.DataNode:
DatanodeRegistration(172.29.2.67:50010,
storageID=DS-739735928-172.29.2.67-50010-1259798617913, infoPort=50075,
ipcPort=50020):DataXceiver
java.net.SocketTimeoutException: 480000 millis timeout while waiting for
channel to be ready for write. ch : java.nio.channels.SocketChannel[connected
local=/172.29.2.67:50010 remote=/172.29.2.67:41058]
at
org.apache.hadoop.net.SocketIOWithTimeout.waitForIO(SocketIOWithTimeout.java:185)
at
org.apache.hadoop.net.SocketOutputStream.waitForWritable(SocketOutputStream.java:159)
at
org.apache.hadoop.net.SocketOutputStream.transferToFully(SocketOutputStream.java:198)
at
org.apache.hadoop.hdfs.server.datanode.BlockSender.sendChunks(BlockSender.java:313)
at
org.apache.hadoop.hdfs.server.datanode.BlockSender.sendBlock(BlockSender.java:400)
at
org.apache.hadoop.hdfs.server.datanode.DataXceiver.readBlock(DataXceiver.java:180)
at
org.apache.hadoop.hdfs.server.datanode.DataXceiver.run(DataXceiver.java:95)
at java.lang.Thread.run(Thread.java:619)
> reduce tasks stall and are eventually killed
> --------------------------------------------
>
> Key: MAPREDUCE-1308
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1308
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: tasktracker
> Environment: 20-node cluster, 8 cores per machine, 32GB memory,
> Fedora Linux
> Reporter: Brian Karlak
>
> We recently migrated our 0.19.2 cluster from Gentoo Linux to Fedora Linux.
> Everything was running smoothly before, but now about 5%-10% of our jobs have
> at least one reduce task that stalls out and is eventually killed with the
> message:
> Task attempt_200912102211_1648_r_000009_0 failed to report status for
> 6003 seconds. Killing!
> The task is then re-launched and completes successfully, usually in a couple
> of minutes.
> This is problematic because our scheduled Hadoop jobs now take an extra
> hour-and-a-half to run (6000 seconds).
> There are no indications in the logs that anything is amiss. The task
> starts, a small amount of the copy/shuffle runs, and then nothing is else is
> heard from the task until it is killed. I will attach the relevant parts of
> the TaskTracker logs in the comments.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
