[
https://issues.apache.org/jira/browse/HDFS-16504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaoqiao He updated HDFS-16504:
-------------------------------
Fix Version/s: 3.4.0
Hadoop Flags: Reviewed
Summary: Add parameter for NameNode to process getBloks request
(was: add `dfs.namenode.get-blocks.check.operation` to enable or disable
checkOperation when NNs process getBlocks)
Committed to trunk. Thanks [~max2049] for your contributions!
> Add parameter for NameNode to process getBloks request
> ------------------------------------------------------
>
> 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
> Assignee: Max Xie
> Priority: Minor
> Labels: pull-request-available
> Fix For: 3.4.0
>
> Time Spent: 2h
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
