[
https://issues.apache.org/jira/browse/HADOOP-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639935#action_12639935
]
Raghu Angadi commented on HADOOP-4358:
--------------------------------------
It seems like getAccessTime() is unnecessarily tied to "precision". Precision
is just a configuration number to help reduce performance impact. "precision"
of 1 hour should not mean all times should be at hour. Am I missing something?
I thought accessTime is just the time when it was 'updated' (currently this
implies when it was written edits.log).
> 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.
