-
Notifications
You must be signed in to change notification settings - Fork 1k
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 number clients reached using subscribe_with_timeout #1259
Comments
casperisfine
pushed a commit
to casperisfine/redis-rb
that referenced
this issue
Apr 2, 2024
Fix: redis#1259 Otherwise we need to wait for GC to close it.
casperisfine
pushed a commit
to casperisfine/redis-rb
that referenced
this issue
Apr 2, 2024
Fix: redis#1259 Otherwise we need to wait for GC to close it.
casperisfine
pushed a commit
to casperisfine/redis-rb
that referenced
this issue
Apr 2, 2024
Fix: redis#1259 Otherwise we need to wait for GC to close it.
This was a bug fixed in #1260. You can point your gemfile at the repo and your code should now work as intended. |
Super! Thanks for the quick turnaround. Will you be releasing a new version of the gem anytime soon? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a Rails 7 app using REDIS for pubsub, hosted on Heroku ("Heroku Data for Redis" add on). This also happens locally (when I set the maxclients down to 20, like is set for the Heroku instance)
Our code sets up REDIS like this:
We listen for pubsub like this:
I want to allow the caller to abort the listening, so I'm trying to change it like this:
However, after 20 loops (on the 21st attempt), I get an error
Alternatively, I've tried putting my
while
loop above the withdrawal from the connection pool:I've also tried removing the connection pool altogether, but still experience the issue.
I've also tried just using the recipe from your README
and still experienced the issue.
Can you help me to get an interruptable subscribe for PUBSUB events?
If via
subscribe_with_timeout
, what is the underlying reason for my error?Thank you
The text was updated successfully, but these errors were encountered: