[
https://issues.apache.org/jira/browse/HDFS-10359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15271076#comment-15271076
]
Daryn Sharp edited comment on HDFS-10359 at 5/4/16 5:52 PM:
------------------------------------------------------------
I don't like this dangerous idea because it would be far too easy for a naive
admin to bury their cluster. I agree with Chris that this should be a script,
but not part of official hdfs.
More importantly, forcing a full block report will not detect missing or
corrupt blocks. The DN will just send its in-memory state.
was (Author: daryn):
I don't like this dangerous idea because it would be far too easy for a naive
admin to bury their cluster. I agree with Chris that this should be a script,
but not part of official hdfs.
More importantly, forcing a full block report will detect missing or corrupt
blocks. The DN will just send its in-memory state.
> 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: [email protected]
For additional commands, e-mail: [email protected]
