[Bug] graph-node stops retrying when block ingestion stops due to RPC issues

[shiyasmohd]

Bug report

When block ingestion stops due to RPC issues, graph-node stops retrying block ingestion. Even after an RPC issue is resolved graph node block ingestor doesn’t recover on itself without restarting the ingestor.

Relevant log output

No response

IPFS hash

No response

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.
• [X] I have searched the issue tracker to make sure this issue is not a duplicate.

OS information

None

[azf20]

thanks @Shiyasmohd! @mangas @leoyvens is this expected, or should we already be retrying in this case?

[steven94kr]

Is there any progess of this issue ? I'm a operator of graph-node. I think it have to resolve... I always restart graph-node manually. And sometime if I missed to check the graph node, there is some downtime in our services to use graph-node because the graph node stopped to sync.... 🙇🏼‍♂️

[azf20]

@mangas do the lazy provider checks help here? #5337