-
Notifications
You must be signed in to change notification settings - Fork 987
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Assertion about dynamic data sources failed #4994
Comments
Some more logs. Here's what I see during indexer startup
Here are 3 different instances of the panic happening
and another
and another
|
This has now happened on a second subgraph completely unrelated to the one above in a different graph node cluster we run. For the one above, we dropped it entirely (and removed all underlying data) then redeployed and everything worked perfectly. I suspect this is a regression in 0.33.0. @leoyvens any ideas here? |
Thanks @paymog
You are saying that this happens intermittently? Is there any pattern to the subgraphs, i.e. is it affecting File Data Sources, or any dynamic data source? |
yup, seems to happen intermittently and only on some subgraphs. I went through the drop and redeploy flow mentioned above for another subgraph today and was surprised to be confronted with this error log after the redeployment
Restarting the indexer fixed the issue. I've never seen this error log before though. It seems to be happening with dynamic data sources and the assertion mentioned seems to be part of the dynamic data sources code path. |
I know of two situations that can trigger this assert:
|
We're running v0.33.0 so I guess the PR should in our build. How would it be that 2 graph nodes attempt to index the same deployment? In the original case and the one I just mentioned, there definitely are multiple nodes running in the cluster. I wonder if this might be related to #5011 and #5014 which are showing issues with assigning subgraphs to specific indexers. |
Sometimes |
We use the JSON API to remove and change assignments, specifically the That being said, we should probably move this specific thread to one of the other issues and keep this issue focused on the assertion failure. |
On |
Yup, that was our experience as well on prior versions of graph node. We never encountered issues like this on v0.33.0. However, for some reason we don't always see that behavior now. |
Happening on another subgraph,
How can we fix this without deleting all of the underlying data? This is especially problematic for subgraphs that take a very long time to index, like uniswap. |
@leoyvens is it safe to downgrade from 0.33.0 to 0.32.0? |
@leoyvens will a new patch version with this fix be released anytime soon? |
Bug report
A subgraph deployed into my graph node is failing with
I'm also seeing issues with the creation of runtime hosts.
Relevant log output
IPFS hash
QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC
Subgraph name or link to explorer
No response
Some information to help us out
OS information
Linux
The text was updated successfully, but these errors were encountered: