[
https://issues.apache.org/jira/browse/HDDS-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16644303#comment-16644303
]
Anu Engineer commented on HDDS-604:
-----------------------------------
There is hardly any unit test for this feature. I have run an ozone cluster and
hand tested this feature.
{code:java}
hadoop@34aa2ebc45f5:~$ ozone getconf -confKey ozone.enabled
true
hadoop@34aa2ebc45f5:~$ ozone getconf -ozonemanagers
ozoneManager{code}
> Correct Ozone getOzoneConf description
> ---------------------------------------
>
> Key: HDDS-604
> URL: https://issues.apache.org/jira/browse/HDDS-604
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Hanisha Koneru
> Assignee: Dinesh Chitlangia
> Priority: Minor
> Labels: newbie
> Attachments: HDDS-604.001.patch
>
>
> The {{./ozone getozoneconf}} subcommand description mentions the subcommand
> as {{getconf}}. We should consistently call it either {{getozoneconf}} or
> {{getconf}} at both places.
> {code:java}
> $ bin/ozone getozoneconf
> 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
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
