[
https://issues.apache.org/jira/browse/HDDS-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695925#comment-17695925
]
Neil Joshi commented on HDDS-7098:
----------------------------------
[~smeng] ,
{quote}Right now Recon only exposes missing container info via
{{/api/v1/containers/missing}} , which is displayed in page
{{/#/MissingContainers}} :
{quote}
The recon UI has been updated to *_also_* include the unhealthy states in page
/#/MissingContainers. In addition the containers unhealthy are exposed to the
api endpoint
{code:java}
api/v1/containers/unhealthy {code}
[~erose] , with the recon api endpoint providing the containers in unhealthy
states, MISSING, UNDER REPLICATED, MIS-REPLICATED, OVER REPLICATED, total
count, container state, and all replicas (see attached image), is there any
additional information we need to provide / update? With what recon provides
with the UI MissingContainers page (container health) and the
/api/vi/containers/unhealthy endpoint does that provide enough info?
!image-2023-03-02-16-01-07-814.png!
> 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, image-2023-03-02-16-01-07-814.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]
