[
https://issues.apache.org/jira/browse/HDDS-17411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chi-Hsuan Huang updated HDDS-17411:
-----------------------------------
Description:
While Recon is initializing, the Namespace Usage page in the new UI shows two
notifications for the same condition:
# The page shows "Information being initialized: Namespace Summary is being
initialized, please wait." for {{{}/namespace/usage{}}}.
# {{NUMetadata}} shows "Metadata Initialization: The metadata is currently
initializing. Please wait a moment and try again later" for
{{{}/namespace/summary{}}}.
Both endpoints return {{INITIALIZING}} from the same
{{ReconUtils.isInitializationComplete}} check. {{NUMetadata}} is only rendered
by the Namespace Usage page, after the page starts fetching usage, so the page
notice always covers this case.
*Proposal*
In {{{}NUMetadata{}}}, keep hiding the summary rows on {{INITIALIZING}} but
drop the {{showDataFetchError}} call, as HDDS-17006 did for quota. Update
{{NUMetadata.test.tsx}} and add a page-level check in
{{NamespaceUsage.test.tsx}} that only one notice is shown.
The {{includes('metadata')}} match in {{showDataFetchError}} is left as is,
since the old UI ({{{}diskUsage.tsx{}}}) still relies on it.
*Repro*
Run {{pnpm dev}} with the mock API returning {{INITIALIZING}} for
{{{}/namespace/usage{}}}, {{/namespace/summary}} and {{{}/namespace/quota{}}},
then open Namespace Usage and load root usage. Screenshot attached.
Related: HDDS-17006
was:
While Recon is initializing, the Namespace Usage page in the new UI shows two
notifications for the same condition:
# The page shows "Information being initialized: Namespace Summary is being
initialized, please wait." for {{/namespace/usage}}.
# {{NUMetadata}} shows "Metadata Initialization: The metadata is currently
initializing. Please wait a moment and try again later" for
{{/namespace/summary}}.
Both endpoints return {{INITIALIZING}} from the same
{{ReconUtils.isInitializationComplete}} check. {{NUMetadata}} is only rendered
by the Namespace Usage page, after the page starts fetching usage, so the page
notice always covers this case.
*Proposal*
In {{NUMetadata}}, keep hiding the summary rows on {{INITIALIZING}} but drop
the {{showDataFetchError}} call, as HDDS-17006 did for quota. Update
{{NUMetadata.test.tsx}} and add a page-level check in
{{NamespaceUsage.test.tsx}} that only one notice is shown.
The {{includes('metadata')}} match in {{showDataFetchError}} is left as is,
since the old UI ({{diskUsage.tsx}}) still relies on it.
*Repro*
Run {{pnpm dev}} with the mock API returning {{INITIALIZING}} for
{{/namespace/usage}}, {{/namespace/summary}} and {{/namespace/quota}}, then
open Namespace Usage and load root usage. Screenshot attached.
Related: HDDS-17006
> Recon UI: show one initialization notice on the Namespace Usage page
> --------------------------------------------------------------------
>
> Key: HDDS-17411
> URL: https://issues.apache.org/jira/browse/HDDS-17411
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone Recon
> Reporter: Chi-Hsuan Huang
> Priority: Minor
> Attachments: Screenshot 2026-10-24 at 10.36.53 AM.png,
> nu-init-master.png
>
>
> While Recon is initializing, the Namespace Usage page in the new UI shows two
> notifications for the same condition:
> # The page shows "Information being initialized: Namespace Summary is being
> initialized, please wait." for {{{}/namespace/usage{}}}.
> # {{NUMetadata}} shows "Metadata Initialization: The metadata is currently
> initializing. Please wait a moment and try again later" for
> {{{}/namespace/summary{}}}.
> Both endpoints return {{INITIALIZING}} from the same
> {{ReconUtils.isInitializationComplete}} check. {{NUMetadata}} is only
> rendered by the Namespace Usage page, after the page starts fetching usage,
> so the page notice always covers this case.
>
>
>
> *Proposal*
> In {{{}NUMetadata{}}}, keep hiding the summary rows on {{INITIALIZING}} but
> drop the {{showDataFetchError}} call, as HDDS-17006 did for quota. Update
> {{NUMetadata.test.tsx}} and add a page-level check in
> {{NamespaceUsage.test.tsx}} that only one notice is shown.
> The {{includes('metadata')}} match in {{showDataFetchError}} is left as is,
> since the old UI ({{{}diskUsage.tsx{}}}) still relies on it.
> *Repro*
> Run {{pnpm dev}} with the mock API returning {{INITIALIZING}} for
> {{{}/namespace/usage{}}}, {{/namespace/summary}} and
> {{{}/namespace/quota{}}}, then open Namespace Usage and load root usage.
> Screenshot attached.
> Related: HDDS-17006
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
