graphprotocol / graphprotocol/indexer

[BUG] store error

Open
#1,068 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
262
Forks
148
PR merge metrics
No merged PRs in 30d

Description

I'm getting many of these errors in the agent when using this version sha-7389527. After I downgrade back to v0.21.11 it stops happening

2024-12-26T09:05:21.382668219Z stdout F {"level":50,"time":1735203921382,"pid":1,"hostname":"indexer-agent-upgrade-0","name":"IndexerAgent","component":"Network","indexer":"0xbdfb5Ee5a2aBF4fc7bB1bD1221067aEf7f9dE491","protocolNetwork":"eip155:42161","operator":"0x8b34351aD4e6fB049c14ADfC90aC5ac8923Ba900","component":"NetworkMonitor","protocolNetwork":"eip155:42161","err":{"type":"IndexerError","message":"Failed to query indexer allocations","stack":"IndexerError: Failed to query indexer allocations\n    at indexerError (/opt/indexer/packages/indexer-common/dist/errors.js:179:12)\n    at NetworkMonitor.allocations (/opt/indexer/packages/indexer-common/dist/indexer-management/monitor.js:150:59)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async AllocationManager.prepareTransactions (/opt/indexer/packages/indexer-common/dist/indexer-management/allocations.js:118:32)\n    at async AllocationManager.executeTransactions (/opt/indexer/packages/indexer-common/dist/indexer-management/allocations.js:37:45)\n    at async AllocationManager.executeBatch (/opt/indexer/packages/indexer-common/dist/indexer-management/allocations.js:21:24)\n    at async /opt/indexer/packages/indexer-common/dist/indexer-management/actions.js:189:33\n    at async /opt/indexer/node_modules/sequelize/lib/sequelize.js:507:18\n    at async ActionManager.executeApprovedActions (/opt/indexer/packages/indexer-common/dist/indexer-management/actions.js:156:9)\n    at async /opt/indexer/packages/indexer-common/dist/indexer-management/actions.js:116:50","code":"IE010","explanation":"https://github.com/graphprotocol/indexer/blob/main/docs/errors.md#ie010","cause":{"type":"CombinedError","message":"[GraphQL] Store error: database unavailable","stack":"CombinedError: [GraphQL] Store error: database unavailable\n    at NetworkSubgraph.query (/opt/indexer/packages/indexer-common/dist/network-subgraph.js:126:29)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async Promise.all (index 0)\n    at async SubgraphFreshnessChecker.checkedQueryRecursive (/opt/indexer/packages/indexer-common/dist/subgraphs.js:243:59)\n    at async NetworkMonitor.allocations (/opt/indexer/packages/indexer-common/dist/indexer-management/monitor.js:98:32)\n    at async AllocationManager.prepareTransactions (/opt/indexer/packages/indexer-common/dist/indexer-management/allocations.js:118:32)\n    at async AllocationManager.executeTransactions (/opt/indexer/packages/indexer-common/dist/indexer-management/allocations.js:37:45)\n    at async AllocationManager.executeBatch (/opt/indexer/packages/indexer-common/dist/indexer-management/allocations.js:21:24)\n    at async /opt/indexer/packages/indexer-common/dist/indexer-management/actions.js:189:33\n    at async /opt/indexer/node_modules/sequelize/lib/sequelize.js:507:18","name":"CombinedError","graphQLErrors":[{"message":"Store error: database unavailable"}]}},"msg":"Failed to query indexer allocations"}

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the logged NetworkMonitor.allocations and NetworkSubgraph.query entry points in packages/indexer-common/dist/indexer-management/monitor.js and network-subgraph.js. Compare sha-7389527 with v0.21.11 and investigate why the GraphQL store reports database unavailable. Done means the regression is reproduced or explained and allocation queries no longer fail under the reported conditions.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql, typescript
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.