[
https://issues.apache.org/jira/browse/HADOOP-3232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587665#action_12587665
]
Johan Oskarsson commented on HADOOP-3232:
-----------------------------------------
Example client exception:
08/04/10 10:09:27 INFO dfs.DFSClient: Exception in createBlockOutputStream
java.io.IOException: Bad connect ack with firstBadLink 10.0.5.76:50010
08/04/10 10:09:27 INFO dfs.DFSClient: Abandoning block blk_-5192866954303337577
08/04/10 10:09:27 INFO dfs.DFSClient: Waiting to find target node:
10.0.5.70:50010
Datanode log output from around the same time:
2008-04-10 10:09:15,758 INFO org.apache.hadoop.dfs.DataNode: Datanode 2 got
response for connect ack from downstream datanode with firstbadlink as
10.0.5.76:50010
2008-04-10 10:09:15,758 INFO org.apache.hadoop.dfs.DataNode: Datanode 2
forwarding connect ack to upstream firstbadlink is 10.0.5.76:50010
2008-04-10 10:09:15,758 INFO org.apache.hadoop.dfs.DataNode: PacketResponder
blk_-9149681676832791404 2 Exception java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readLong(DataInputStream.java:399)
at
org.apache.hadoop.dfs.DataNode$PacketResponder.run(DataNode.java:1822)
at java.lang.Thread.run(Thread.java:619)
2008-04-10 10:09:15,758 INFO org.apache.hadoop.dfs.DataNode: PacketResponder 2
for block blk_-9149681676832791404 terminating
2008-04-10 10:09:16,793 INFO org.apache.hadoop.dfs.DataNode: writeBlock
blk_1511572447827516117 received exception java.net.SocketTimeoutException:
Read timed out
2008-04-10 10:09:16,793 ERROR org.apache.hadoop.dfs.DataNode:
10.0.5.70:50010:DataXceiver: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.net.SocketInputStream.read(SocketInputStream.java:182)
at java.io.DataInputStream.readByte(DataInputStream.java:248)
at org.apache.hadoop.io.WritableUtils.readVLong(WritableUtils.java:324)
at org.apache.hadoop.io.WritableUtils.readVInt(WritableUtils.java:346)
at org.apache.hadoop.io.Text.readString(Text.java:413)
at
org.apache.hadoop.dfs.DataNode$DataXceiver.writeBlock(DataNode.java:1117)
at org.apache.hadoop.dfs.DataNode$DataXceiver.run(DataNode.java:938)
at java.lang.Thread.run(Thread.java:619)
2008-04-10 10:09:23,895 INFO org.apache.hadoop.dfs.DataNode: Receiving block
blk_-7442302015902809712 src: /10.0.5.74:55546 dest: /10.0.5.74:50010
2008-04-10 10:09:23,896 INFO org.apache.hadoop.dfs.DataNode: Datanode 0
forwarding connect ack to upstream firstbadlink is
2008-04-10 10:09:23,927 INFO org.apache.hadoop.dfs.DataNode: Received block
blk_-7442302015902809712 of size 902 from /10.0.5.74
2008-04-10 10:09:23,928 INFO org.apache.hadoop.dfs.DataNode: PacketResponder 0
for block blk_-7442302015902809712 terminating
2008-04-10 10:09:23,937 INFO org.apache.hadoop.dfs.DataNode: Receiving block
blk_4161972554165500020 src: /10.0.11.7:41256 dest: /10.0.11.7:50010
2008-04-10 10:09:23,968 INFO org.apache.hadoop.dfs.DataNode: Datanode 2 got
response for connect ack from downstream datanode with firstbadlink as
2008-04-10 10:09:23,969 INFO org.apache.hadoop.dfs.DataNode: Datanode 2
forwarding connect ack to upstream firstbadlink is
2008-04-10 10:09:24,034 INFO org.apache.hadoop.dfs.DataNode: Received block
blk_4161972554165500020 of size 95 from /10.0.11.7
2008-04-10 10:09:24,034 INFO org.apache.hadoop.dfs.DataNode: PacketResponder 2
for block blk_4161972554165500020 terminating
2008-04-10 10:09:27,664 INFO org.apache.hadoop.dfs.DataNode: Datanode 2 got
response for connect ack from downstream datanode with firstbadlink as
10.0.5.76:50010
2008-04-10 10:09:27,664 INFO org.apache.hadoop.dfs.DataNode: Datanode 2
forwarding connect ack to upstream firstbadlink is 10.0.5.76:50010
2008-04-10 10:09:27,665 INFO org.apache.hadoop.dfs.DataNode: PacketResponder
blk_-5192866954303337577 2 Exception java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:180)
at java.io.DataInputStream.readLong(DataInputStream.java:399)
at
org.apache.hadoop.dfs.DataNode$PacketResponder.run(DataNode.java:1822)
at java.lang.Thread.run(Thread.java:619)
> Datanodes time out
> ------------------
>
> Key: HADOOP-3232
> URL: https://issues.apache.org/jira/browse/HADOOP-3232
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.16.2
> Environment: 10 node cluster + 1 namenode
> Reporter: Johan Oskarsson
> Priority: Critical
> Fix For: 0.16.3
>
>
> I recently upgraded to 0.16.2 from 0.15.2 on our 10 node cluster.
> Unfortunately we're seeing datanode timeout issues. In previous versions
> we've often seen in the nn webui that one or two datanodes "last contact"
> goes from the usual 0-3 sec to ~200-300 before it drops down to 0 again.
> This causes mild discomfort but the big problems appear when all nodes do
> this at once, as happened a few times after the upgrade.
> It was suggested that this could be due to namenode garbage collection, but
> looking at the gc log output it doesn't seem to be the case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
