[HADOOP-19096] [ABFS] Enhancing Client-Side Throttling Metrics Updation Logic

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.1
• Fix Version/s: 3.5.0, 3.4.1
• Component/s: fs/azure
• Labels: pull-request-available
• Target Version/s: 3.4.1
• Assignee: Anuj Modi
• Reporter: Anuj Modi
• Created: 29/Feb/24 10:05
• Updated: 14/Nov/24 06:28
• Resolved: 11/Apr/24 13:12

Description

ABFS has a client-side throttling mechanism which works on the metrics collected from past requests made. I requests are getting failed due to throttling at server, we update our metrics and client side backoff is calculated based on those metrics.

This PR enhances the logic to decide which requests should be considered to compute client side backoff interval as follows:

For each request made by ABFS driver, we will determine if they should contribute to Client-Side Throttling based on the status code and result:

1. Status code in 2xx range: Successful Operations should contribute.
2. Status code in 3xx range: Redirection Operations should not contribute.
3. Status code in 4xx range: User Errors should not contribute.
4. Status code is 503: Throttling Error should contribute only if they are due to client limits breach as follows:
   1. 503, Ingress Over Account Limit: Should Contribute
   2. 503, Egress Over Account Limit: Should Contribute
   3. 503, TPS Over Account Limit: Should Contribute
   4. 503, Other Server Throttling: Should not Contribute.
5. Status code in 5xx range other than 503: Should not Contribute.
6. IOException and UnknownHostExceptions: Should not Contribute.

Issue Links

• links to: GitHub Pull Request #6276
• links to: GitHub Pull Request #6720