[
https://issues.apache.org/jira/browse/HDFS-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HDFS-528:
-----------------------------
Attachment: hdfs-528-v2.txt
Here is a new patch which solves the same problem, but does so by adding
another condition for safemode during startup.
A new conf dfs.safemode.min.datanodes determines how many datanodes it should
wait to be "alive" before exiting safemode.
To test this I updated TestSafeMode, and also moved that test into
o.a.h.hdfs.server.namenode so that it could access the package-protected
getSafeModeTip() function in FSNamesystem.
> Add dfsadmin -waitDatanodes feature to block until DNs have reported
> --------------------------------------------------------------------
>
> Key: HDFS-528
> URL: https://issues.apache.org/jira/browse/HDFS-528
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: scripts
> Affects Versions: 0.21.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: hdfs-528-v2.txt, hdfs-528.txt
>
>
> When starting up a fresh cluster programatically, users often want to wait
> until DFS is "writable" before continuing in a script. "dfsadmin -safemode
> wait" doesn't quite work for this on a completely fresh cluster, since when
> there are 0 blocks on the system, 100% of them are accounted for before any
> DNs have reported.
> This JIRA is to add a command which waits until a certain number of DNs have
> reported as alive to the NN.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
