[
https://issues.apache.org/jira/browse/HDFS-16209?focusedWorklogId=646729&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-646729
]
ASF GitHub Bot logged work on HDFS-16209:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 06/Sep/21 01:45
Start Date: 06/Sep/21 01:45
Worklog Time Spent: 10m
Work Description: tomscut commented on pull request #3378:
URL: https://github.com/apache/hadoop/pull/3378#issuecomment-913278183
@ayushtkn @ferhui @virajjasani Thank you very much for your comments and
suggestions. I think what you are saying is reasonable, we should not change
the default value of this parameter. But we can add a caption, as @virajjasani
said.
I have changed the parameter description information, please have a look.
Thanks again.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 646729)
Time Spent: 1h 40m (was: 1.5h)
> 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
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> 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.
> !namenode-write-lock.jpg!
>
> 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-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
