[jira] [Commented] (HDFS-16504) Add parameter for NameNode to process getBloks request

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HDFS-16504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17615622#comment-17615622 ] 

ASF GitHub Bot commented on HDFS-16504:
---------------------------------------

Neilxzn commented on PR #4068:
URL: https://github.com/apache/hadoop/pull/4068#issuecomment-1274363227

   这是自动回复邮件。来件已接收，谢谢。




> 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.10#820010)

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