Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

[Feature] Add weighted load balancing support for RPC providers

Aberta
  • Algo errado?
#6,104 2 comentários 0 reações 1 responsável Ver no GitHub

@DaMandal0rian já está trabalhando nisso.

Desde 14/8/2025.

Avaliação

Esta issue ainda não foi avaliada.

Descrição

enhancement Stale

Problem

Currently, Graph Node uses a sequential failover approach for RPC providers. It attempts to use the first configured provider and only moves to the next provider if there are issues or if a required feature is not available. This means traffic is not distributed across providers - instead, the first healthy provider handles all requests until it fails.

This limitation prevents operators from:

  • Distributing load across multiple healthy RPC endpoints
  • Utilizing all available RPC capacity efficiently
  • Preventing single provider overload when multiple endpoints are available
  • Optimizing costs by balancing requests across providers with different pricing
  • Achieving true high availability through active load distribution

Proposed Solution

Implement weighted random load balancing for RPC provider selection, allowing operators to configure traffic distribution percentages for each endpoint.

Example Use Cases
  1. Performance-based routing: Direct 80% of traffic to a high-performance dedicated node and 20% to a backup
  2. Cost optimization: Route 90% to cheaper endpoints and 10% to premium endpoints for critical requests
  3. Gradual rollout: Start a new provider at 5% traffic and increase as confidence grows
  4. Capacity management: Distribute load according to each endpoint's actual capacity

Implementation

I've created PR #[YOUR_PR_NUMBER] that adds this functionality with:

  • Configurable decimal weights (0.0-1.0) per RPC provider
  • New --weighted-rpc-steering CLI flag and config option
  • Backward compatibility (defaults to equal weights when not specified)
  • Weighted random selection algorithm for provider choice
Configuration Example
[chains.mainnet]
weighted_rpc_steering = true
provider = [
 { 
   label = "primary-node",
   details = { type = "web3", url = "https://fast.example.com", weight = 0.7 }
 },
 { 
   label = "secondary-node", 
   details = { type = "web3", url = "https://medium.example.com", weight = 0.2 }
 },
 { 
   label = "backup-node",
   details = { type = "web3", url = "https://backup.example.com", weight = 0.1 }
 }
]

Related Work

  • PR - Implementation of weighted load balancing
  • This addresses a common request for managing multiple RPC endpoints with varying characteristics
Are you aware of any blockers that must be resolved before implementing this feature? If so, which? Link to any relevant GitHub issues.

No response

Some information to help us out
  • Tick this box if you plan on implementing this feature yourself.
  • I have searched the issue tracker to make sure this issue is not a duplicate.
Linguagem predominante
Rust
Estrelas
3.2k
Forks
1.1k
Nenhum PR com merge em 30d

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de graphprotocol/graph-node

Todas as issues de graphprotocol/graph-node

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.