graphprotocol / graphprotocol/graph-node
[Feature] Support multiple ingestor nodes
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
Description
The graph node config file currently only supports a single block ingestor like so
[chains]
ingestor = "block_ingestor_node"
It would be great if we could configure different nodes to ingest different chains, for example have one node ingest mainnet(s) and another ingest testnet(s). One idea would be to use the same rule logic for assigning deployments to indexers.
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.
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
Start by tracing how the graph node config file parses the [chains] ingestor setting, then inspect the existing rule logic for assigning deployments to indexers. Determine how multiple ingestor nodes could be configured for different chains, and define completion as separate nodes successfully ingesting their assigned mainnet or testnet chains without disrupting current single-ingestor configurations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, blockchain, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100