hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9503) Replace -namenode option with -fs for NNThroughputBenchmark
Date Tue, 02 Feb 2016 06:00:44 GMT

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

Konstantin Shvachko commented on HDFS-9503:
-------------------------------------------

Hey Vinayakumar. The patch will indeed take {{fs.defaultFS}} from a config file and treat
it as a remote NameNode, which is different from current behaviour. Although, it is easy to
override the configuration value with the same {{-fs}} option just introduced. The following
will use local NN no matter what is in the {{core-site.xml}}
{code}
NNThroughtputBenchmark -conf core-site.xml -fs local -op mkdirs
NNThroughtputBenchmark -conf core-site.xml -fs file:/// -op mkdirs
{code}
I don't know if it is incompatible, just saying everything can be controlled on the command
line for the benchmark.

As I mentioned in HDFS-7847 I don't understand the use case for a remote NN in the context
of NNThroughtputBenchmark, but at least now we will avoid introducing unnecessary options
with this patch.

+1 for the patch

> 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
>          Components: test
>            Reporter: Konstantin Shvachko
>            Assignee: Mingliang Liu
>         Attachments: HDFS-9053.000.patch, HDFS-9053.001.patch, HDFS-9053.002.patch, HDFS-9053.003.patch,
HDFS-9053.004.patch, HDFS-9053.005.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)

Mime
View raw message