[Bug] Graph-node doesn't restart connections to Firehose

[trader-payne]

Bug report

Subgraphs stop at random times without being able to restart their connections to Firehose. The only way to kick them back to a working state is to restart the graph-node.

Relevant log output

Dec 21 17:00:49.054 ERRO An error occurred while streaming blocks: status: Cancelled, message: "source canceled", details: [], metadata: MetadataMap { headers: {} }, provider: firehose, deployment: QmcskbugoHafPJC4EcFzkPNc2ExNPY8L32QagCn5qrtQU5, sgd: 88, subgraph_id: QmcskbugoHafPJC4EcFzkPNc2ExNPY8L32QagCn5qrtQU5, component: FirehoseBlockStream
Dec 21 17:00:49.976 ERRO Unable to connect to endpoint: status: Unknown, message: "transport error", details: [], metadata: MetadataMap { headers: {} }: transport error: connection error: connection reset: connection reset, provider: firehose, deployment: QmcskbugoHafPJC4EcFzkPNc2ExNPY8L32QagCn5qrtQU5, sgd: 88, subgraph_id: QmcskbugoHafPJC4EcFzkPNc2ExNPY8L32QagCn5qrtQU5, component: FirehoseBlockStream

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

Linux

[azf20]

@trader-payne are you still seeing this issue? Does it only try to reconnect once?

[github-actions[bot]]

Looks like this issue has been open for 6 months with no activity. Is it still relevant? If not, please remember to close it.