[
https://issues.apache.org/jira/browse/AMBARI-26619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Himanshu Maurya updated AMBARI-26619:
-------------------------------------
Description:
The {{usePolling}} hook triggers API calls at fixed intervals without checking
if the previous call has completed. This creates a cascading problem where
multiple identical API requests are in-flight simultaneously.
*Impact on Application:*
# {*}Network Congestion{*}: Multiple identical requests in flight
simultaneously
# {*}Race Conditions{*}: Responses arriving out of order causing state
inconsistencies
# {*}Server Load{*}: Backend processing duplicate requests unnecessarily
# {*}Memory Pressure{*}: Multiple promise chains and response objects in memory
# {*}UI Freezes{*}: Multiple callbacks processing large response data
simultaneously (contributing to 1+ second blocking tasks)
# {*}Wasted Resources{*}: Network bandwidth, CPU cycles, memory for duplicate
data
# {*}Cascading Updates{*}: Multiple state updates from overlapping responses
trigger mass re-renders
*Evidence from Analysis:*
* 3 overlapping polling loops running at 5-second intervals
* No abort mechanism for in-flight requests
* No queue management for pending calls
* API responses can take 3-8 seconds but polling interval is only 5 seconds
* Contributes to 467 long tasks and constant UI updates
was:
Implement the hosts list page with all the functionalities as in existing
ambari-web ui.
All the functionalities should be same and the new ui should be same or better
as compared to existing ui.
> Ambari Web React: Fix Polling Implementation - No Pending Request Check in
> Ambari Modern UI
> -------------------------------------------------------------------------------------------
>
> Key: AMBARI-26619
> URL: https://issues.apache.org/jira/browse/AMBARI-26619
> Project: Ambari
> Issue Type: Story
> Reporter: Himanshu Maurya
> Assignee: Himanshu Maurya
> Priority: Major
> Fix For: 3.1.0
>
>
> The {{usePolling}} hook triggers API calls at fixed intervals without
> checking if the previous call has completed. This creates a cascading problem
> where multiple identical API requests are in-flight simultaneously.
> *Impact on Application:*
> # {*}Network Congestion{*}: Multiple identical requests in flight
> simultaneously
> # {*}Race Conditions{*}: Responses arriving out of order causing state
> inconsistencies
> # {*}Server Load{*}: Backend processing duplicate requests unnecessarily
> # {*}Memory Pressure{*}: Multiple promise chains and response objects in
> memory
> # {*}UI Freezes{*}: Multiple callbacks processing large response data
> simultaneously (contributing to 1+ second blocking tasks)
> # {*}Wasted Resources{*}: Network bandwidth, CPU cycles, memory for
> duplicate data
> # {*}Cascading Updates{*}: Multiple state updates from overlapping responses
> trigger mass re-renders
> *Evidence from Analysis:*
> * 3 overlapping polling loops running at 5-second intervals
> * No abort mechanism for in-flight requests
> * No queue management for pending calls
> * API responses can take 3-8 seconds but polling interval is only 5 seconds
> * Contributes to 467 long tasks and constant UI updates
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
