devabhishekpal opened a new pull request, #5154:
URL: https://github.com/apache/ozone/pull/5154

   ## What changes were proposed in this pull request?
   
   With the current code for Recon UI, we are not handling scenarios where 
network requests should be cancelled when user is shifting pages/context.
   This causes unnecessary requests to be made.
   
   For example if the user opens the Recon UI and selects a view, then the user 
changes that view immediately, the request for the previous view will still go 
through, along with the new request for the changed view.
   This is more noticeable in a slow network, where requests might be stuck in 
a pending state, and during that time if we switch the view the previous 
request will still be sent, along with the new request.
   
   The scenario is attached in the video recording, where a slow 3G network is 
being emulated.
   If we are clicking on DiskUsage view it sends a request to:
   
   `.../du?path=/&files=true`
   
   Now if we click on the Containers view the second request is being sent for:
   
   `.../unhealthy`
   
   At this point we will notice both the requests to be in a pending state. And 
later both the requests are resolved.
   Ideally we should be cancelling the DiskUsage request the moment we shift to 
the container view.
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-9124
   
   
   ## How was this patch tested?
   
   The patch was tested manually.
   
   
https://github.com/apache/ozone/assets/43001336/e5b2bef5-443d-4cd1-8aa5-ab5fc921c6dd
   
   


-- 
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