You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Soya Miyoshi (Jira)" <ji...@apache.org> on 2019/09/04 01:42:00 UTC

[jira] [Assigned] (HDFS-14817) [Dynamometer] start-dynamometer-cluster.sh shows its usage even if correct arguments are given.

     [ https://issues.apache.org/jira/browse/HDFS-14817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Soya Miyoshi reassigned HDFS-14817:
-----------------------------------

    Assignee: Soya Miyoshi

> [Dynamometer] start-dynamometer-cluster.sh shows its usage even if correct arguments are given.
> -----------------------------------------------------------------------------------------------
>
>                 Key: HDFS-14817
>                 URL: https://issues.apache.org/jira/browse/HDFS-14817
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: tools
>            Reporter: Soya Miyoshi
>            Assignee: Soya Miyoshi
>            Priority: Major
>
> When trying to launch the infrastructure application to begin the startup of the internal HDFS cluster as shown in the Manual Workload Launch section in [here|https://aajisaka.github.io/hadoop-document/hadoop-project/hadoop-dynamometer/Dynamometer.html]
>  {code:|borderStyle=solid}
> $ ./dynamometer-infra/bin/start-dynamometer-cluster.sh \
>  -hadoop_binary_path hadoop-3.0.2.tar.gz \
>  -conf_path my-hadoop-conf \
>  -fs_image_dir hdfs:///fsimage \
>  -block_list_path hdfs:///dyno/blocks
> {code}
>  its usage is always shown even if correct arguments are given, if `-hadoop_binary_path` is placed as a first argument for the script.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org