[
https://issues.apache.org/jira/browse/HADOOP-3232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587708#action_12587708
]
Johan Oskarsson commented on HADOOP-3232:
-----------------------------------------
Found 68 of these when doing a stackdump in a datanode that had lost contact
with the namenode.
"[EMAIL PROTECTED]" daemon prio=10 tid=0x7192bc00 nid=0x5bc6 waiting for
monitor entry [0x70cee000..0x70cef0c0]
java.lang.Thread.State: BLOCKED (on object monitor)
at org.apache.hadoop.dfs.FSDataset.getFile(FSDataset.java:867)
- waiting to lock <0x77ce9360> (a org.apache.hadoop.dfs.FSDataset)
at org.apache.hadoop.dfs.FSDataset.isValidBlock(FSDataset.java:795)
at org.apache.hadoop.dfs.FSDataset.writeToBlock(FSDataset.java:614)
at
org.apache.hadoop.dfs.DataNode$BlockReceiver.<init>(DataNode.java:1995)
at
org.apache.hadoop.dfs.DataNode$DataXceiver.writeBlock(DataNode.java:1074)
at org.apache.hadoop.dfs.DataNode$DataXceiver.run(DataNode.java:938)
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
>
> Attachments: hadoop-hadoop-datanode.out,
> hadoop-hadoop-namenode-master2.out
>
>
> 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.
