[
https://issues.apache.org/jira/browse/HDFS-10359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15270024#comment-15270024
]
Tao Jie commented on HDFS-10359:
--------------------------------
[~kihwal], [~cnauroth], [~arpitagarwal], [~linyiqun] Thank you for reply！
I understand that trigger block report for all datanode would bring too much
presure for namenode.
Our scenario is we use *setrep -w* command to ensure replications of blocks on
all datanodes sometime. Blocks on datanode may lost somehow, however namenode
would not notice block missing until block report in 6 hours. In this case, we
suppose to trigger block report for all datanodes before *setrep -w*. Further
more, if we want to set replication of blocks to 1, some blocks may corrupt.
It is OK to use a script to trigger block report from all datenodes, or just
restart namenode.
I am not very familiar with this logic, if I am wrong or there is a better way,
please correct me.
> Allow trigger block report from all datanodes
> ---------------------------------------------
>
> Key: HDFS-10359
> URL: https://issues.apache.org/jira/browse/HDFS-10359
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode
> Affects Versions: 2.7.0, 2.6.1
> Reporter: Tao Jie
>
> Since we have HDFS-7278 allows trigger block report from one certain
> datanode. It would be helpful to add a option to this command to trigger
> block report from all datanodes.
> Command maybe like this:
> *hdfs dfsadmin -triggerBlockReport \[-incremental\]
> <datanode_host:ipc_port|all>*
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
