microsoftgraph / microsoftgraph/msgraph-sdk-dotnet
Retry handler smart queue
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 789
- Forks
- 264
- Avg merge
- 15h 17m
- Merged PRs (30d)
- 3
Description
Concurrent calls can hit the same throttling limit. We want separate threads that hit the same throttling limit to co-respect the throttling limit.
Throttling limits are workload specific. This means that we need to manage retry queues based on calls to the same backend. We will need a heuristic, workload map, and/or regex to determine whether a retry call needs to be added to a queue.
This will require investigation and design spec. The design will be applicable across platforms but we will implement for .Net.
AB#7330
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by investigating the existing .NET retry handler and how throttling responses identify workloads; then write the requested design spec for a workload-aware shared retry queue and validate the approach before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100