priyeshkaratha commented on PR #10420:
URL: https://github.com/apache/ozone/pull/10420#issuecomment-4621681679

   > @priyeshkaratha So as discussed offline, keep the behavior of page 
consistent in terms of refresh of page because Pending Deletion card also there 
on page. So better when UI already polling and continue to poll till refresh of 
page by calling respective APIs once they finish their execution, we should 
also call Pending Deletion APIs and refresh their data on the page.
   
   @devmadhuu I changed implementation with auto refresh option only.
   
   The workflow is as follows:
   
   -  When the page is opened, the UI invokes the following APIs:
   
   ```
   /storageDistribution
   /pendingDeletion?component=om
   /pendingDeletion?component=scm
   ```
   These APIs return results immediately.
   
   - For `/pendingDeletion?component=dn`, the API initially returns an 
in-progress status. The UI then starts polling this API every 5 seconds. Once 
DataNode metric collection completes successfully, the API returns the final 
result and the UI is updated accordingly.
   - The auto-refresh interval is configured to 1 minute. If cluster metric 
collection completes within a reasonable timeframe (for example, 10–30 
seconds), the workflow remains smooth and consistent. Every minute, the UI 
refreshes and shows a loading state only until the updated result becomes 
available.
   - Additionally, there is a 30-second delay between metric collection cycles. 
After a collection completes, the next collection will not start for at least 
30 seconds. This ensures that users can view stable results for a reasonable 
period before a new collection begins.
   Overall, I believe this approach provides a more consistent and predictable 
user experience.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to