graphprotocol / graphprotocol/indexer
IE005 errors when closing/opening allocations
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 262
- Forks
- 148
- PR merge metrics
- No merged PRs in 30d
Description
So one of the issues seen right now on our baremetal setup is the IE005 errors after each closing/opening allocations cycle we do.
graph node: v0.30.0
graph indexer: 0.20.11
OS: ubuntu 20.04
setup: binaries (systemd)
Here is how it looks in our grafana:
Note the uptick of the errors, that is when we were doing allocations. You can ignore the other errors seen on the screenshot.
Also note that a simple restart of the indexer service resolves the issue, but even without restart i believe those errors just happen upon allocations, once that is done, it doesnt grow anymore
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 reproducing the allocation closing/opening cycle on the reported bare-metal setup with Graph Node v0.30.0, Graph indexer 0.20.11, Ubuntu 20.04, and systemd binaries, then inspect the IE005 errors and their behavior after an indexer restart. The report names no source files or tests; done means the cycle no longer causes recurring IE005 errors without requiring a restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grafana, typescript, ubuntu
- Domain
- backend, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100