[
https://issues.apache.org/jira/browse/HADOOP-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639666#action_12639666
]
Konstantin Shvachko commented on HADOOP-4358:
---------------------------------------------
> I think we should round off atime to int before passing to INode.
This will be inconsistent with getAccessTime(). Or do you propose to "unround"
it back after getting access time.
The more I think about it the more inconsistent it appears. If we store a
rounded aTime, then shutdown the cluster, and restart it with a different
precision configuration parameter. Then the stored value does not make any
sense. It looks like we cannot have the precision configured. It must be a
constant. Is that right?
> 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
> Priority: Blocker
> Fix For: 0.19.0
>
>
> 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.
