hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4533) start-dfs.sh ignored additional parameters besides -upgrade
Date Mon, 18 Mar 2013 19:14:15 GMT

    [ https://issues.apache.org/jira/browse/HDFS-4533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605492#comment-13605492
] 

Colin Patrick McCabe commented on HDFS-4533:
--------------------------------------------

I think I would rather have something like this:

{code}
usage="Usage: start-dfs.sh [-upgrade|-rollback] [-nnOpt <additional NameNode options>]
{code}

that way you could do something like this:
{code}
./start-dfs.sh -nnOpt '-clusterId 123'
{code}

That way, it would be easy for us to add a way to pass options to the {{JournalNode}}, {{DataNode}},
etc. in the future.  Just dumping everything we can't parse into the NameNode arguments seems
suboptimal... and will prevent us giving helpful error messages when the user messes up.
                
> start-dfs.sh ignored additional parameters besides -upgrade
> -----------------------------------------------------------
>
>                 Key: HDFS-4533
>                 URL: https://issues.apache.org/jira/browse/HDFS-4533
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode, namenode
>    Affects Versions: 2.0.3-alpha
>            Reporter: Fengdong Yu
>              Labels: patch
>             Fix For: 2.0.5-beta
>
>         Attachments: HDFS-4533.patch
>
>
> start-dfs.sh only takes -upgrade option and ignored others. 
> So If run the following command, it will ignore the clusterId option.
> start-dfs.sh -upgrade -clusterId 1234

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message