Performance: add round robin node selection
Open
Nobody has claimed this yet.
p2
- Dominant language
- TypeScript
- Stars
- 11
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Add the possibility to aim at multiple nodes instead of a single one in the config of the provider.
The nodes could be cycled in round robin for queries and with automatic fallback on failure.
Contributor guide
No contributing guide indexed for this repository
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
Start by locating the provider configuration and the code that sends queries to a configured node. Determine how multiple nodes can be represented, then trace query failures to understand where fallback belongs. Done means nodes are selected in round-robin order and a failed node automatically falls back to another configured node.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100