[jira] [Commented] (HDDS-14927) Add Quasi-Closed Container Tracking in Recon.

["Ethan Rose (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HDDS-14927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18069700#comment-18069700 ] 

Ethan Rose commented on HDDS-14927:
-----------------------------------

I'm +1 for making this easier to access from the API, but quasi-closed containers are not necessarily unhealthy, so I don't think we should put them in the UI. I don't think we should be grouping them in with corrupted, under-replicated, and mis-replicated containers. Container balancer should work independently of quasi-closed containers. That is a shortcoming that needs to be improved in SCM, not Recon.

> Add Quasi-Closed Container Tracking in Recon.
> ---------------------------------------------
>
>                 Key: HDDS-14927
>                 URL: https://issues.apache.org/jira/browse/HDDS-14927
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: Ozone Recon
>            Reporter: Arafat Khan
>            Assignee: Arafat Khan
>            Priority: Major
>              Labels: pull-request-available
>
> Introduce support in Recon to track *QUASI_CLOSED containers* and expose their associated DataNodes and mapped keys within the Unhealthy Containers section. This involves designing a backend approach (either leveraging Replication Manager logic or a custom Recon pipeline) to identify quasi-closed containers, reusing existing mapping logic such as {{*containerManager.getLatestContainerHistory(...)*}} where applicable, and enabling APIs/UI to list containers and drill down into their key mappings. The goal is to improve visibility and debugging of quasi-closed containers, especially for operational readiness before running processes like the Container Balancer.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org