-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Max recursion depth RecursionError when max clients exceeded with Sentinel #2866
Comments
@rad-pat Can you confirm that now you don't get this error (with code from master) and we can close this issue? |
@dvora-h I can confirm that the bug is not fixed on master. The code above still fails with max recursion error. I would think this is related to the |
One important point to note is that I do not get the error with version 4.5.5 |
Thanks for the response. I will try to find & fix the problem |
I can also confirm that it happens without Sentinel too, and also without async.
|
Apologies, this was incorrect information, the problem is still there with 4.5.5 |
Version: redis-py 4.6.0, redis
Platform: Python 3.11.4 on Debian
Description:
Similar to a bug reported here #2563.
When maximum number of clients are used up for a Sentinel, there is an issue with the health check that causes a maximum recursion
Exception:
** Code to reproduce **
The health check is deliberately made short to generate the error
The text was updated successfully, but these errors were encountered: