Open
Description
Bug report
We have recently upgraded our graph node for the first time in months to v0.36.0. Since upgrading we face an issue: every new subgraph that is deployed will not start indexing unless we restart the graph node. Any ideas why this could be happening? We have quite a few production users including DEX's etc so its a bit of a pain. The issue is identical on our testnet and mainnet graph nodes.
The node is connected to our L2 network.
{
"errors": [
{
"message": "Store error: query execution failed: Subgraph QmRzL2dZraVoMCniN5iJ88ygCVuT24ix8T12Zv724z2ug8 has not started syncing yet. Wait for it to ingest a few blocks before querying it"
}
]
}
Note: the included logs appear after the node is restarted. For 12 hours before hand we get the error above and nothing related to the subgraph in the logs
Relevant log output
Jan 17 10:04:17.117 INFO Resolve subgraph files using IPFS, n_templates: 0, n_data_sources: 7, runner_index: 29, sgd: 793, subgraph_id: QmRzL2dZraVoMCniN5iJ88ygCVuT24ix8T12Zv724z2ug8, component: SubgraphInstanceManager
Jan 17 10:04:23.074 INFO Successfully resolved subgraph files using IPFS, features: ø, n_templates: 0, n_data_sources: 7, runner_index: 29, sgd: 793, subgraph_id: QmRzL2dZraVoMCniN5iJ88ygCVuT24ix8T12Zv724z2ug8, component: SubgraphInstanceManager
Jan 17 10:04:23.282 INFO Starting subgraph writer, queue_size: 5, runner_index: 29, sgd: 793, subgraph_id: QmRzL2dZraVoMCniN5iJ88ygCVuT24ix8T12Zv724z2ug8, component: SubgraphInstanceManager
Jan 17 10:04:23.848 INFO Data source count at start: 7, runner_index: 29, sgd: 793, subgraph_id: QmRzL2dZraVoMCniN5iJ88ygCVuT24ix8T12Zv724z2ug8, component: SubgraphInstanceManager
Jan 17 10:04:24.670 INFO Scanning blocks [8200000, 8200000], target_range_size: 1, sgd: 793, subgraph_id: QmRzL2dZraVoMCniN5iJ88ygCVuT24ix8T12Zv724z2ug8, component: BlockStream
Jan 17 10:04:24.776 INFO Scanned blocks [8200000, 8200000], range_size: 1, sgd: 793, subgraph_id: QmRzL2dZraVoMCniN5iJ88ygCVuT24ix8T12Zv724z2ug8, component: BlockStream
(Continues scanning as exptected)IPFS hash
QmRzL2dZraVoMCniN5iJ88ygCVuT24ix8T12Zv724z2ug8
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
Linux