[
https://issues.apache.org/jira/browse/HDFS-9503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15118820#comment-15118820
]
Vinayakumar B commented on HDFS-9503:
-------------------------------------
bq. If not specified, the default file system URI will be file:///. Otherwise,
it should be hdfs://host:port format, parsed by GenericOptionsParser. Perhaps
we don't need another flag to indicate new NN instance or remote NN?
This is not quite right. This makes the restriction that, core-site.xml also
should not have changed the 'fs.defaultFS' configuration.
bq. I think, Since -fs is already provided by default, Now just need another
flag ( may be instead of -namenode) to mention whether to use New Namenode
instance, or just connect to remote namenode.
What I mean by this is, both configuring 'fs.defaultFS' or specifying '-fs' to
'hdfs://localhost:port' are same.
Only thing we need to inform {{NNThroughputBenchmark}} is whether to use
existing running Namenode (might be remote or on same node) or create its own
instance. This we can do by having another option as flag ( instead of
-namenode ) like, "-remotenamenode". If this present, then makes use of '-fs'
or 'fs.defaultFS' option. Else creates its own Namenode.
Since this change is incompatible,
If anybody out there feels these changes are not required?
> Replace -namenode option with -fs for NNThroughputBenchmark
> -----------------------------------------------------------
>
> Key: HDFS-9503
> URL: https://issues.apache.org/jira/browse/HDFS-9503
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Konstantin Shvachko
> Assignee: Mingliang Liu
> Attachments: HDFS-9053.000.patch, HDFS-9053.001.patch,
> HDFS-9053.002.patch
>
>
> HDFS-7847 introduced a new option {{-namenode}}, which is intended to point
> the benchmark to a remote NameNode. It should use a standard generic option
> {{-fs}} instead, which is routinely used to specify NameNode URI in shell
> commands.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
