[
https://issues.apache.org/jira/browse/HDDS-9700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787356#comment-17787356
]
Ethan Rose commented on HDDS-9700:
----------------------------------
Great improvement, these are the papercut issues that really hurt when
something serious is already wrong with the cluster. {{jq}} is actually able to
process individual json objects the same as a list, but it would still be nice
to have the output as list so it is considered well formed json. For errors in
only some of the containers, as long as the output goes to stderr it should not
affect piping to jq.
> Allow ozone admin container info to list multiple containers
> ------------------------------------------------------------
>
> Key: HDDS-9700
> URL: https://issues.apache.org/jira/browse/HDDS-9700
> Project: Apache Ozone
> Issue Type: Improvement
> Components: SCM Client
> Reporter: Stephen O'Donnell
> Assignee: Stephen O'Donnell
> Priority: Major
>
> Currently the command:
> {code}
> ozone admin container info 1234
> {code}
> Only accepts a single container ID. If you need to list the details from many
> containers, then the JVM startup overhead makes the command very slow.
> Therefore it would be useful to allow a list of IDs to be specified so a
> single JVM instance can retrieve all the details in a single call.
> The logic should handle invalid IDs and "unknown to SCM containers" by
> printing an error and continuing to the next ID rather than failing.
> For the JSON output, it probably makes sense to output a JSON array rather
> than a series of individual JSON blob, so the entire output can be pass to a
> JSON tool without modification.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
