[
https://issues.apache.org/jira/browse/HDFS-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032719#comment-13032719
]
Todd Lipcon commented on HDFS-1905:
-----------------------------------
I agree that cluster ID is a nicer construct than namespace ID. But it doesn't
replace it, since we still have the namespaceID in NNStorage.
Perhaps a nice compromise would be the following:
- "hadoop namenode -format" gains a required argument for cluster ID. ie
"hadoop namenode -format mycluster". If you don't specify this it should print
usage info.
- "hadoop namenode -upgrade" by default will carry over the old namespaceID as
the new cluster's cluster ID? Alternatively one may provide a cluster ID with
"hadoop namenode -upgrade -clusterid foo"?
Another question: if cluster ID is meant to be a user-visible "nice name" --
how can one rename a cluster?
> Improve the usability of namenode -format
> ------------------------------------------
>
> Key: HDFS-1905
> URL: https://issues.apache.org/jira/browse/HDFS-1905
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Bharath Mundlapudi
> Assignee: Bharath Mundlapudi
> Priority: Minor
> Fix For: 0.23.0
>
>
> While setting up 0.23 version based cluster, i ran into this issue. When i
> issue a format namenode command, which got changed in 23, it should let the
> user know to how to use this command in case where complete options were not
> specified.
> ./hdfs namenode -format
> I get the following error msg, still its not clear what and how user should
> use this command.
> 11/05/09 15:36:25 ERROR namenode.NameNode:
> java.lang.IllegalArgumentException: Format must be provided with clusterid
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:1483)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1623)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1689)
>
> The usability of this command can be improved.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
