[
https://issues.apache.org/jira/browse/HDFS-14678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16910767#comment-16910767
]
Leon Gao commented on HDFS-14678:
---------------------------------
Yes we need this in branch 2, I will create another PR for this.
> Allow triggerBlockReport to a specific namenode
> -----------------------------------------------
>
> Key: HDFS-14678
> URL: https://issues.apache.org/jira/browse/HDFS-14678
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode
> Affects Versions: 2.8.2
> Reporter: Leon Gao
> Assignee: Leon Gao
> Priority: Major
> Fix For: 3.3.0
>
>
> In our largest prod cluster (running 2.8.2) we have >3k hosts. Every time
> when rolling restarting NNs we will need to wait for block report which takes
> >2.5 hours for each NN.
> One way to make it faster is to manually trigger a full block report from all
> datanodes. [HDFS-7278|https://issues.apache.org/jira/browse/HDFS-7278].
> However, the current triggerBlockReport command will trigger a block report
> on all NNs which will flood the active NN as well.
> A quick solution will be adding an option to specify a NN that the manually
> triggered block report will go to, something like:
> *_hdfs dfsadmin [-triggerBlockReport [-incremental] <datanode_host:ipc_port>]
> [-namenode] <namenode_host:ipc_port>_*
> So when doing a restart of standby NN or observer NN we can trigger an
> aggressive block report to a specific NN to exit safemode faster without
> risking active NN performance.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
