You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Doug (Jira)" <ji...@apache.org> on 2022/03/25 10:17:00 UTC

[jira] [Comment Edited] (HADOOP-18171) NameNode Access Time Precision

    [ https://issues.apache.org/jira/browse/HADOOP-18171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512231#comment-17512231 ] 

Doug edited comment on HADOOP-18171 at 3/25/22, 10:16 AM:
----------------------------------------------------------

Hey Akira will you please explain how current setting is impacting now ? which is 1 hour.


was (Author: JIRAUSER287001):
Hey Akira will you please explain how current setting is working now ? which is 1 hour.

> NameNode Access Time Precision
> ------------------------------
>
>                 Key: HADOOP-18171
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18171
>             Project: Hadoop Common
>          Issue Type: Improvement
>         Environment: As of now we are on CDH version 6.3.4 and we are planning to upgrade it to CDP version 7.1.4. for that cloudera want us to disable namenode property dfs.access.time.precision by changing it's value to 0. Current value for this property is 1 hour. so my question is that how this value is impacting in current scenario? what is the effect of that and what will happen If I make it to zero.
>            Reporter: Doug
>            Priority: Major
>         Attachments: namenodeaccesstime.png
>
>




--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org