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

Posted to hdfs-dev@hadoop.apache.org by "tomscut (Jira)" <ji...@apache.org> on 2021/09/03 04:21:00 UTC

[jira] [Created] (HDFS-16209) Set dfs.namenode.caching.enabled to false as default

tomscut created HDFS-16209:
------------------------------

             Summary: Set dfs.namenode.caching.enabled to false as default
                 Key: HDFS-16209
                 URL: https://issues.apache.org/jira/browse/HDFS-16209
             Project: Hadoop HDFS
          Issue Type: Improvement
    Affects Versions: 3.1.0
            Reporter: tomscut
            Assignee: tomscut


Namenode config:
dfs.namenode.write-lock-reporting-threshold-ms=50ms
dfs.namenode.caching.enabled=true (default)

 

In fact, the caching feature is not used in our cluster, but this switch is turned on by default(dfs.namenode.caching.enabled=true), incurring some additional write lock overhead. We count the number of write lock warnings in a log file, and find that the number of rescan cache warnings reaches about 32%, which greatly affects the performance of Namenode.

 

We should set 'dfs.namenode.caching.enabled' to false by default and turn it on when we wants to use it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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