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 2022/03/14 03:03:00 UTC
[jira] [Updated] (HDFS-16504) add `dfs.namenode.get-blocks.check.operation` to enable or disable checkOperation when NNs process getBlocks
[ https://issues.apache.org/jira/browse/HDFS-16504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HDFS-16504:
----------------------------------
Labels: pull-request-available (was: )
> add `dfs.namenode.get-blocks.check.operation` to enable or disable checkOperation when NNs process getBlocks
> ------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-16504
> URL: https://issues.apache.org/jira/browse/HDFS-16504
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: balancer & mover, namanode
> Affects Versions: 3.4.0
> Reporter: Max Xie
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> HDFS-13183 add a nice feature that Standby NameNode can process getBlocks request to reduce Active load. Namenode must set `dfs.ha.allow.stale.reads = true` to enable this feature. However, if we set `dfs.ha.allow.stale.reads = true`, Standby Namenode will be able to process all read requests, which may lead to yarn jobs fail because Standby Namenode is stale .
> Maybe we should add a config `dfs.namenode.get-blocks.check.operation=false` for namenode to disable check operation when namenode process getBlocks request.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org