[
https://issues.apache.org/jira/browse/HDFS-14817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924452#comment-16924452
]
Hudson commented on HDFS-14817:
-------------------------------
FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #17243 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/17243/])
HDFS-14817. [Dynamometer] Fix start script options parsing which (xkrogen: rev
9637097ef9b213fcbeffa2538ccb7e0aaabde9c4)
* (edit)
hadoop-tools/hadoop-dynamometer/hadoop-dynamometer-infra/src/main/java/org/apache/hadoop/tools/dynamometer/Client.java
> [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
> Fix For: 3.3.0
>
> Attachments: HDFS-14817.001.patch, HDFS-14817.002.patch,
> HDFS-14817.003.patch
>
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
