hadoop-hdfs-issues mailing list archives

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

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

Vinayakumar B commented on HDFS-9503:

This is  incompatible change, not because of replacing {{-namenode}} with {{-fs}} ( because,
2.8 which has -namenode not released yet),
But because, current patch will change the startup behavior.

Before patch, if '-namenode' was not given, then benchmark used to run in standalone mode,
still using the 'fs.defaultFS' conf for namenode's RPC address.
Now with patch, if 'fs.defaultFS' is provided, either via configuration or '-fs', benchmark
expects that as Remote NameNode.
And to run standalone mode to test Replication op specifically, 'fs.defaultFS' conf needs
to be removed from site xmls.

If this is okay, may be its better to update the corresponding DOCs and Release Notes.

Other than this, current changes in patch looks good to me.

> 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

View raw message