[
https://issues.apache.org/jira/browse/HADOOP-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640328#action_12640328
]
Raghu Angadi commented on HADOOP-4358:
--------------------------------------
We caught one of the nodes in this state in last couple of minutes. 'sda' was
very busy and the remaining disks were idle. Logs and os also reside on sda..
ssh login took more than a minute. This can explain why reading a block could
take so long. Still not sure what causes the load on sda alone. we have
datanode log for this node. Didn't have much time to take jstack and other info.
> NPE from CreateEditsLog
> -----------------------
>
> Key: HADOOP-4358
> URL: https://issues.apache.org/jira/browse/HADOOP-4358
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs, test
> Affects Versions: 0.19.0
> Reporter: Chris Douglas
> Assignee: Raghu Angadi
> Priority: Blocker
> Fix For: 0.19.0
>
> Attachments: HADOOP-4358.patch
>
>
> HADOOP-1869 added a call to setAccessTime(long) from the INode cstr, which
> relies on a non-null value from FSNamesystem::getFSNamesystem.
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.hadoop.hdfs.server.namenode.INode.setAccessTime(INode.java:301)
> at org.apache.hadoop.hdfs.server.namenode.INode.<init>(INode.java:99)
> at
> org.apache.hadoop.hdfs.server.namenode.INodeDirectory.<init>(INodeDirectory.java:45)
> at
> org.apache.hadoop.hdfs.CreateEditsLog.addFiles(CreateEditsLog.java:68)
> at org.apache.hadoop.hdfs.CreateEditsLog.main(CreateEditsLog.java:214)
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
