[
https://issues.apache.org/jira/browse/HDFS-11806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006100#comment-16006100
]
Doris Gu edited comment on HDFS-11806 at 5/11/17 8:41 AM:
----------------------------------------------------------
Since "hdfs journalnode" only has general options, I add a brief statement
about journalnode followed the style of secondary namenode.
{quote}[root@localhost ~]# hdfs journalnode -h
Usage: hdfs journalnode
JournalNode is a necessary role in a typical HA cluster with QJM. It
allows a NameNode to read and write edit logs stored on it's local disk. Note
that you should run an odd number of JNs, (i.e. 3, 5, 7, etc.), since edit log
modifications must be written to a majority of JNs.
Generic options supported are
-conf <configuration file> specify an application configuration file
-D <property=value> use value for given property
-fs <local|namenode:port> specify a namenode
-jt <local|resourcemanager:port> specify a ResourceManager
-files <comma separated list of files> specify comma separated files to be
copied to the map reduce cluster
-libjars <comma separated list of jars> specify comma separated jar files to
include in the classpath.
-archives <comma separated list of archives> specify comma separated
archives to be unarchived on the compute machines.
The general command line syntax is
bin/hadoop command [genericOptions] [commandOptions]{quote}
Please check, thanks in advance!
was (Author: doris):
Since "hdfs journalnode" only has general options, I add a brief statement
about journalnode followed the style of secondary namenode.
{quote}[root@localhost ~]# hdfs journalnode -h
Usage: hdfs journalnode
JournalNode is a necessary role in a typical HA cluster with QJM. It
allows a NameNode to read and write edit logs stored on it's local disk. Note
that you should run an odd number of JNs, (i.e. 3, 5, 7, etc.), since edit log
modifications must be written to a majority of JNs.
Generic options supported are
-conf <configuration file> specify an application configuration file
-D <property=value> use value for given property
-fs <local|namenode:port> specify a namenode
-jt <local|resourcemanager:port> specify a ResourceManager
-files <comma separated list of files> specify comma separated files to be
copied to the map reduce cluster
-libjars <comma separated list of jars> specify comma separated jar files to
include in the classpath.
-archives <comma separated list of archives> specify comma separated
archives to be unarchived on the compute machines.
The general command line syntax is
bin/hadoop command [genericOptions] [commandOptions]{quote}
> hdfs journalnode command should support meaningful --help
> ---------------------------------------------------------
>
> Key: HDFS-11806
> URL: https://issues.apache.org/jira/browse/HDFS-11806
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 3.0.0-alpha2
> Reporter: Doris Gu
>
> Most (sub) commands support -help or -h options for detailed help while hdfs
> journalnode does not. What's worse, when you use "hdfs journalnode -h" to get
> some help, journalnode daemon starts straightly.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
