[
https://issues.apache.org/jira/browse/HDFS-14678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16909403#comment-16909403
]
Hudson commented on HDFS-14678:
-------------------------------
FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #17137 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/17137/])
HDFS-14678. Allow triggerBlockReport to a specific namenode. (#1252). (weichiu:
rev 9a1d8cfaf50ec29ffb2d8522ba2f4bc6605d8b8b)
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataNode.java
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/tools/TestDFSAdmin.java
* (edit)
hadoop-hdfs-project/hadoop-hdfs-client/src/main/proto/ClientDatanodeProtocol.proto
* (edit)
hadoop-hdfs-project/hadoop-hdfs-client/src/main/java/org/apache/hadoop/hdfs/client/BlockReportOptions.java
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/protocolPB/ClientDatanodeProtocolServerSideTranslatorPB.java
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HDFSCommands.md
* (edit)
hadoop-hdfs-project/hadoop-hdfs-client/src/main/java/org/apache/hadoop/hdfs/protocolPB/ClientDatanodeProtocolTranslatorPB.java
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/datanode/TestTriggerBlockReport.java
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/DFSAdmin.java
> 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
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
