You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know how to reliably reproduce this, but I'm finding that on v0.33.0 often times when a subgraph gets removed, it doesn't actually stop indexing until the graph node restarts. I suspect this is related to #5011.
I'm running a multi node cluster (this has happened in a two node cluster and a 10 node cluster) with sharding. So far I've only seen this issue happen with subgraphs that are on firehose enabled chains that are erroring.
I will keep this ticket updated as I find more info.
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.
I have searched the issue tracker to make sure this issue is not a duplicate.
OS information
None
The text was updated successfully, but these errors were encountered:
Thanks @paymog - I don't know if this will be provider related. As this is a multi node cluster, maybe the issue is flakiness at that level, or do you see this consistently (i.e. never stops indexing, or sometimes doesn?)
Bug report
I don't know how to reliably reproduce this, but I'm finding that on v0.33.0 often times when a subgraph gets removed, it doesn't actually stop indexing until the graph node restarts. I suspect this is related to #5011.
I'm running a multi node cluster (this has happened in a two node cluster and a 10 node cluster) with sharding. So far I've only seen this issue happen with subgraphs that are on firehose enabled chains that are erroring.
I will keep this ticket updated as I find more info.
Relevant log output
No response
IPFS hash
No response
Subgraph name or link to explorer
No response
Some information to help us out
OS information
None
The text was updated successfully, but these errors were encountered: