Namit Maheshwari created HDDS-532:
-------------------------------------
Summary: ozone getozoneconf help shows the name as getconf
Key: HDDS-532
URL: https://issues.apache.org/jira/browse/HDDS-532
Project: Hadoop Distributed Data Store
Issue Type: Bug
Reporter: Namit Maheshwari
{code:java}
[root@ctr-e138-1518143905142-481027-01-000002 bin]# ./ozone getozoneconf -help
ozone getconf is utility for getting configuration information from the config
file.
ozone getconf
[-includeFile] gets the include file path that defines the datanodes that can
join the cluster.
[-excludeFile] gets the exclude file path that defines the datanodes that need
to decommissioned.
[-ozonemanagers] gets list of Ozone Manager nodes in the cluster
[-storagecontainermanagers] gets list of ozone storage container manager
nodes in the cluster
[-confKey [key]] gets a specific key from the configuration
Generic options supported are:
-conf <configuration file> specify an application configuration file
-D <property=value> define a value for a given property
-fs <file:///|hdfs://namenode:port> specify default filesystem URL to use,
overrides 'fs.defaultFS' property from configurations.
-jt <local|resourcemanager:port> specify a ResourceManager
-files <file1,...> specify a comma-separated list of files to be copied to the
map reduce cluster
-libjars <jar1,...> specify a comma-separated list of jar files to be included
in the classpath
-archives <archive1,...> specify a comma-separated list of archives to be
unarchived on the compute machines
The general command line syntax is:
command [genericOptions] [commandOptions]
{code}
Now the utility name is "getozoneconf", whereas the help shows the as "getconf"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
