[
https://issues.apache.org/jira/browse/HDFS-9503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mingliang Liu updated HDFS-9503:
--------------------------------
Attachment: HDFS-9053.003.patch
Thanks for your kind remind, [~shv]. The v3 patch is the latest one rebased
from {{trunk}} branch. I deleted the unrelated changes like using a map for
{{datanodes}}. I added this because I met problems when running
{{BlockReportStats}} sub-test against a remote NN. I'll file a new jira if it's
a potential bug.
Meanwhile, I'm still thinking about [~vinayrpet]'s comment as I'm not quite
sure if another option is required, in order to indicate new namenode instance
creation. So his concern was not addressed in the v3 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-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)
