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
[Ent] Occasional Redis::CommandError in concurrent limiter #3854
Comments
That kind of error would happen if your code manually checked out a Redis connection from the connection pool to use for pubsub. Do you have any app code doing pubsub? If so, show me the subscriber code. |
No, we don't really use pubsub. Anything else you can think of that can be related? |
I can't see how that can happen normally. Can you show me your initializer? |
Can I email it to you? |
Of course, support at contribsys.com |
I don't see any smoking guns in the initializer either. It's a little more complicated than usual but it's not doing anything abnormal with Redis. |
Ok, it's not critical for us, happened just couple times in total. Let me know if you have any ideas how we can help debug this |
I just noticed something in a logs that might be related. So I had these 2 workers that I stopped manually and here's what I saw in a log: Log
|
Those two errors are actually normal in that flow: those jobs were already pushed back to
|
Ok, good to know. The issue with |
Yeah, still no idea what's causing that. |
Is sidekiq using pub/sub internally? I also had this idea, what if I try to use separate redis pool for limiters, do you think it might help? Thanks |
Sidekiq Pro’s Config subsystem uses a subscriber thread to listen for
real-time config changes. That’s the only usage of pub/sub by Sidekiq.
…On Tue, Jul 3, 2018 at 7:44 AM, Dmitry Krasnoukhov ***@***.*** > wrote:
Is sidekiq using pub/sub internally? I also had this idea, what if I try
to use separate redis pool for limiters, do you think it might help? Thanks
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3854 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAALXzrqTM_0Lt8e0VKZzw7TNXVO_Lu7ks5uC4M7gaJpZM4UVpxU>
.
|
See #3886 |
Yup, that's it. I just discovered the same thing this Thursday, but wanted to make sure that was the case first before following up. I'll close this as a duplicate and post my finding on #3886 since it has more useful info in there already |
Ruby version: 2.5.1
Sidekiq / Pro / Enterprise version(s): 5.1.3 / 4.0.3 / 1.7.1
This is a message of exception that we're getting sometimes, seems like it's coming from limiter's scripting code.
Here's how we use the limiter:
Backtrace
I noticed that
sidekiq-ent@1.7.1
has something about lua errors, any chance this is related? Thanks!The text was updated successfully, but these errors were encountered: