[
https://issues.apache.org/jira/browse/HDDS-17504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Priyesh Karatha reassigned HDDS-17504:
--------------------------------------
Assignee: Priyesh Karatha
> Recon UI: show OM purgeable and snapshot-held breakdown on the Capacity and
> Buckets pages
> ------------------------------------------------------------------------------------------
>
> Key: HDDS-17504
> URL: https://issues.apache.org/jira/browse/HDDS-17504
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: Ozone Recon
> Reporter: Priyesh Karatha
> Assignee: Priyesh Karatha
> Priority: Major
>
> The Capacity page's Pending Deletion card shows one OM number. It doesn't say
> how much can be purged now and how much is held by snapshots. The Buckets
> page shows no per-bucket data held by snapshots.
> Proposed change:
> - Capacity → Pending Deletion → OZONE MANAGER:
> - The headline is PURGEABLE + SNAPSHOT HELD, shown as a stacked bar.
> - Below the bar, show PURGEABLE DIRECTORIES and PURGEABLE KEYS as sizes.
> Show N/A when OM doesn't report them.
> - Show a spinner while the status is NOT_STARTED or IN_PROGRESS, and poll
> every 5s.
> - When the status is FAILED, show an error card with the server's message
> instead of an endless spinner.
> - While OM is still collecting, count it as 0 in the page-level PENDING
> DELETION total instead of showing NaN.
> - Buckets page:
> - Add Trapped Bytes and Trapped Keys columns, both sortable.
> - Show "Computing…" until the values are collected.
> - Other:
> - CapacityDetail gets an optional sizes[] row under the bar.
> - The OM types, defaults, mocks (including api/db.json) and
> Capacity.test.tsx are updated, with a new test for the FAILED state.
> Depends on: the Recon API Jira above.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
