Skip to content
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] Removed subgraph does not get removed until graph node restart #5014

Closed
2 of 3 tasks
paymog opened this issue Nov 23, 2023 · 3 comments
Closed
2 of 3 tasks

[Bug] Removed subgraph does not get removed until graph node restart #5014

paymog opened this issue Nov 23, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@paymog
Copy link

paymog commented Nov 23, 2023

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

  • 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

@paymog paymog added the bug Something isn't working label Nov 23, 2023
@azf20
Copy link
Contributor

azf20 commented Dec 1, 2023

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?)

@paymog
Copy link
Author

paymog commented Dec 4, 2023

To be honest I only saw this one time and have no idea how to reproduce it. Will definitely let you know if this happens again.

@azf20
Copy link
Contributor

azf20 commented Dec 4, 2023

OK - will close for now, please re-open if it does, thanks!

@azf20 azf20 closed this as not planned Won't fix, can't repro, duplicate, stale Dec 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants