[
https://issues.apache.org/jira/browse/HDFS-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13600732#comment-13600732
]
Todd Lipcon commented on HDFS-4592:
-----------------------------------
+1
> Default values for access time precision are out of sync between
> hdfs-default.xml and the code
> ----------------------------------------------------------------------------------------------
>
> Key: HDFS-4592
> URL: https://issues.apache.org/jira/browse/HDFS-4592
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.0.4-alpha
> Reporter: Aaron T. Myers
> Assignee: Aaron T. Myers
> Priority: Minor
> Attachments: HDFS-4592.patch
>
>
> In {{hdfs-default.xml}} we have:
> {code}
> <property>
> <name>dfs.namenode.accesstime.precision</name>
> <value>3600000</value>
> <description>The access time for HDFS file is precise upto this value.
> The default value is 1 hour. Setting a value of 0 disables
> access times for HDFS.
> </description>
> </property>
> {code}
> But in {{FSNamesystem}} we have:
> {code}
> this.accessTimePrecision =
> conf.getLong(DFS_NAMENODE_ACCESSTIME_PRECISION_KEY, 0);
> {code}
> We properly define {{DFS_NAMENODE_ACCESSTIME_PRECISION_DEFAULT}} in
> DFSConfigKeys.java, but it's not actually referenced anywhere in the code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
