Sometimes one of the subgraphs stops indexing without errors, while others continue syncing. The only way to fix it is to restart the whole indexer. Every time it is a different subgraph. It doesn't matter if it is self-written or forked from a hosted service using an IPFS hash.
I'm deploying the graph-node to Kubernetes, to the same cluster with the Ethereum node (erigon) and Postgresql. Version is 0.28.2 with GRAPH_KILL_IF_UNRESPONSIVE set to true.
The logs are clear. The indexer stops producing records related to the stuck subgraph_id at all.
I have not found related issues, so I kindly ask for tips on diagnosing a problem in my setup.
Screenshots from Grafana for subgraph Qmca1arSe9U94sHVpzzdUKizNyqFddsXnBZYqkALmSdSRE https://thegraph.com/hosted-service/subgraph/indexed-finance/indexed as an example.
Sometimes one of the subgraphs stops indexing without errors, while others continue syncing. The only way to fix it is to restart the whole indexer. Every time it is a different subgraph. It doesn't matter if it is self-written or forked from a hosted service using an IPFS hash.
I'm deploying the
graph-nodeto Kubernetes, to the same cluster with the Ethereum node (erigon) and Postgresql. Version is0.28.2withGRAPH_KILL_IF_UNRESPONSIVEset totrue.The logs are clear. The indexer stops producing records related to the stuck
subgraph_idat all.I have not found related issues, so I kindly ask for tips on diagnosing a problem in my setup.
Screenshots from Grafana for subgraph
Qmca1arSe9U94sHVpzzdUKizNyqFddsXnBZYqkALmSdSREhttps://thegraph.com/hosted-service/subgraph/indexed-finance/indexed as an example.