You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/09/06 09:27:00 UTC
[jira] [Work logged] (HDFS-16209) Add description for
dfs.namenode.caching.enabled
[ https://issues.apache.org/jira/browse/HDFS-16209?focusedWorklogId=646814&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-646814 ]
ASF GitHub Bot logged work on HDFS-16209:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 06/Sep/21 09:26
Start Date: 06/Sep/21 09:26
Worklog Time Spent: 10m
Work Description: tomscut commented on pull request #3378:
URL: https://github.com/apache/hadoop/pull/3378#issuecomment-913495313
> @tomscut @virajjasani, Thanks. I think It's a good way to add description here.
> BTW, change the title of JIRA and PR.
Thanks @ferhui for your reply. I changed the title of JIRA and PR.
--
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-unsubscribe@hadoop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 646814)
Time Spent: 2h (was: 1h 50m)
> Add description for dfs.namenode.caching.enabled
> ------------------------------------------------
>
> 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: 2h
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org