Arafat Khan created HDDS-14548:
----------------------------------
Summary: Container Mismatch Table: Duplicate API calls triggered
on filter change
Key: HDDS-14548
URL: https://issues.apache.org/jira/browse/HDDS-14548
Project: Apache Ozone
Issue Type: Bug
Components: Ozone Recon
Reporter: Arafat Khan
When switching the "Exists At" filter in the Container Mismatch table,
duplicate API calls are triggered with one being immediately cancelled.
*Steps to Reproduce:*
# Navigate to OM DB Insights → Container Mismatch table
# Click "Exists At" dropdown and select "OM" or "SCM"
# Observe network requests
Expected: Single API call with correct *missingIn* parameter.
*Actual:* Two API calls are triggered:
* First call is cancelled
* Second call completes successfully
{code:java}
mismatch?limit=1000&missingIn=SCM (canceled)
mismatch?limit=1000&missingIn=SCM 200 {code}
{*}Impact{*}: Unnecessary network requests; may cause race conditions in UI
state
*Root Cause (Suspected):* The *{{useEffect}}* hook in
*containerMismatchTable.tsx*
(line 96-98) may be triggering refetch before state is fully updated, causing
double calls
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
