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
Containers getSchema throwing "hit infinite loop" #22243
Comments
Can you try clearing Redis cache? this can be cause by lock in the cache that wasnt properly cleared |
From the code I notice there is no flow path for what has to happen after the MAX_ATTEMPTS has been reached. I can make a PR that fixes that, since it should probably fall back to attempt fetching the schema itself. In a single container the retry logic doesn't make sense either, since there could be multiple requests waiting on the getSchema, causing all of them to be very close together when timing out. |
I just realised that the schema isn't being cached to redis at all. Seems like this |
Before diving into the code have you tried clearing the redis cache as asked?
Thats not missing i think as it's likely not supposed to do that, the actual schema is stored with |
Yes I did clear the cache. |
I had this exact same issue when upgrading to 10.10.5 for our development setup. I ended up removing the |
This is related to #22161 |
Describe the Bug
When our containers are scaling we found many of them crashing, looking at the logs we found this error.
This started happening after updating from 10.9.3 to 10.10.7
To Reproduce
Scale up to multiple containers running directus 10.10.7
Directus Version
v10.0.7
Hosting Strategy
Self-Hosted (Docker Image)
The text was updated successfully, but these errors were encountered: