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
Pipelining commands on a Redis instance is deprecated and will be removed in Redis 5.0.0 (WARNING) #5178
Comments
|
That’s from the Redis gem. 6.4.1 will be released Monday and fix it.
Downgrade that gem or use Sidekiq’s main branch if you want an immediate
fix.
…On Thu, Feb 3, 2022 at 16:30 NemyaNation ***@***.***> wrote:
Ruby version: ruby 2.6.6p146
Rails version: Rails 6.1.3.1
Sidekiq / Pro / Enterprise version(s): 6.4.0
This just started a coulple of hours ago, approximiately ever 2s I get
more than 100 lines of this warning repeated again and again since the
latest update to (6.4.0)
warning in logs:
app[web] info redis.pipelined do
app[web] info redis.get("key")
app[web] info end
app[web] info
app[web] info should be replaced by
app[web] info
app[web] info redis.pipelined do |pipeline|
app[web] info pipeline.get("key")
app[web] info end
app[web] info
app[web] info (called from /app/vendor/bundle/ruby/2.7.0/gems/sidekiq-6.4.0/lib/sidekiq/api.rb:57:in `block in fetch_stats_fast!'}
Feb 4 00:09:38 my-app app[web] info Pipelining commands on a Redis instance is deprecated and will be removed in Redis 5.0.0.
initializers/sidekiq.rb
Sidekiq.configure_server do |config|
config.redis = {
url: ENV["REDISCLOUD_URL"]
}
end
Sidekiq.configure_client do |config|
config.redis = {
url: ENV["REDISCLOUD_URL"],
size: 2
}
end
Sidekiq.strict_args!(false)
Still clogging up my logs, and this is just from live polling on the
dashboard.
I thought it might be fixed by adding Sidekiq.strict_args!(false) but
this did not help, doesn't look like it's from my end and instead something
needs to be updated in the gem itself?
—
Reply to this email directly, view it on GitHub
<#5178>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAAWX7ZGBUE6OBMPVXOZFTUZMMYXANCNFSM5NQNBESQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
@mperham brilliant, no I'll wait, I just was wondered if you guys were aware the latest update was causing this warning. will leave open until monday and I see that the warning has subsided. |
|
I just updated to Sidekiq 6.4.1 and running Rails 7 with Redis 4.6, this is still an issue. Logs fill continuously with notice about using pipeline key. |
|
Do you use any other Sidekiq extensions? |
|
Thanks for the fix, my logs are empty now. Rail 7.0.1, Sidekiq 6.4.1, sidekiq-congestion 0.1.1 and Redis 4.6.0 on Ubuntu 20.04.3 LTS. |
No. My gemfile is "redis" and "sidekiq" |
Ack. NVM... Was just a bad bundle |
|
I'm also still getting the warning on my logs. This is the env information. and the redis was installed using homebrew. |
|
@celsoMartins It's in |
|
The following PRs have been opened by people experiencing the same issue in other gems: |
|
gem redis 4.6 and sidekiq 6.4.1 works for me. |
|
I am still getting the warnings after upgrading sidekiq from 4.2.10 to 6.4.1 or 6.4.0 and even tried using the main branch from Sidekiq. |
|
It may be due to other gems, in my case it was sidekiq-cron. Here is a discussion and fix in forked branch: sidekiq-cron/sidekiq-cron#310 (comment) |
|
Thanks, it worked for me. The issue was with sidekiq-cron. |
Ruby version: ruby 2.6.6p146
Rails version: Rails 6.1.3.1
Sidekiq / Pro / Enterprise version(s): 6.4.0
This just started a coulple of hours ago, approximiately ever 2s I get more than 100 lines of this warning repeated again and again since the latest update to (6.4.0)
warning in logs:
initializers/sidekiq.rbStill clogging up my logs, and this is just from live polling on the dashboard.
I thought it might be fixed by adding
Sidekiq.strict_args!(false)but this did not help, doesn't look like it's from my end and instead something needs to be updated in the gem itself?The text was updated successfully, but these errors were encountered: