[
https://issues.apache.org/jira/browse/HDDS-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17682709#comment-17682709
]
Ethan Rose commented on HDDS-7098:
----------------------------------
For doing this in Recon UI, you would need to check with [~zitadombi] for the
current status and best approach. For doing it in the CLI, we print the replica
information for a given container with {{ozone admin container info--json
<id>}}, but it is not displayed in {{ozone admin container list}}. So to do
this out of the box with the current CLI you could do a container list, and for
each ID in the list get the info, then use jq to filter the replica state for
unhealthy.
This might be more streamlined from the CLI when {{curl}}ing from recon if we
modify {{UnHealthyContainerStates}} to have a state that says "some replicas
unhealthy". Then we could get those container IDs from recon and use {{ozone
admin container info --json <id>}} for each to get replica information, instead
of needing to get and filter all containers client side.
> Provide a way for admin to identify all unhealthy container replicas
> --------------------------------------------------------------------
>
> Key: HDDS-7098
> URL: https://issues.apache.org/jira/browse/HDDS-7098
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ethan Rose
> Assignee: Devesh Kumar Singh
> Priority: Major
> Attachments: MissingContainers.png
>
>
> Currently UNHEALTHY is a state that a container replica can be in
> (ContainerReplicaProto#State), but not a state that the container can be in
> overall (LifeCycleState). This means {{ozone admin container list}} has no
> info about unhealthy containers, because it currently does not print replica
> information. [Recon's
> API|https://ozone.apache.org/docs/current/interface/reconapi.html] and UI
> does not expose replica information either. The only way to determine
> unhealthy containers is to run {{ozone admin container info <ID>}} for a
> container that is already suspected to have unhealthy replicas. This jira
> aims to provide a way to identify and filter container replica states,
> through either Recon's UI, Recon's REST API, or client CLI.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
