graphprotocol / graphprotocol/graph-node
[Bug] graph-node stops retrying when block ingestion stops due to RPC issues
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
Bug report
When block ingestion stops due to RPC issues, graph-node stops retrying block ingestion.
Even after an RPC issue is resolved graph node block ingestor doesn’t recover on itself without restarting the ingestor.
Relevant log output
No response
IPFS hash
No response
Subgraph name or link to explorer
No response
Some information to help us out
- Tick this box if this bug is caused by a regression found in the latest release.
- Tick this box if this bug is specific to the hosted service.
- I have searched the issue tracker to make sure this issue is not a duplicate.
OS information
None
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 or tests are named. Start by locating the block ingestion entry point and the RPC failure and retry handling; reproduce an ingestion stop, restore RPC access, and trace why recovery does not occur. Done means ingestion resumes automatically after RPC recovery without restarting the ingestor, with regression coverage for that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100