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 "Chao Sun (JIRA)" <ji...@apache.org> on 2019/07/30 00:06:00 UTC
[jira] [Commented] (HDFS-14678) Allow triggerBlockReport to a
specific namenode
[ https://issues.apache.org/jira/browse/HDFS-14678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16895664#comment-16895664 ]
Chao Sun commented on HDFS-14678:
---------------------------------
cc [~jojochuang]: could you add [~LeonG] as contributor and assign this JIRA to him? also it would be great if you know whether this issue has been raised before or not :) - it is one of the items we want to improve in H2.
> 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
> Priority: Minor
>
> 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
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org