Skip to content

Indexing stucks until restart #4146

Closed
Closed

Description

@serjvanilla

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.

image

image

Activity

  1. added
    bugSomething isn't working
    on Nov 7, 2022
  2. azf20 commented on Nov 7, 2022

    @azf20
    Contributor

    hey @serjvanilla thanks for the report - are you able to run your Graph Node with GRAPH_LOG=trace to see if you get further details on the affected subgraph?

  3. serjvanilla commented on Nov 8, 2022

    @serjvanilla
    Author

    Indexer redeployed with GRAPH_LOG=trace. Still, no stops since, but I'm continuously watching it. I will try to find more info in that logs as soon as any subgraph stops again.

  4. azf20 commented on Nov 29, 2022

    @azf20
    Contributor

    Hi @serjvanilla closing this for now, but please do re-open if you saw stops as you described above!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions