"Sidekiq connecting to redis" on every rake task

[timon]

Hi all,

I noticed that starting with Sidekiq 7 I always have this line of output whenever I run any rake task in my rails app (e.g. rake db:test:prepare):

2023-03-14T12:59:31.424Z pid=38183 tid=1ju7 INFO: Sidekiq 7.0.5 connecting to Redis with options {:size=>5, :pool_name=>"internal", :url=>nil}

We're using sidekiq-pro, and our intializer is fairly trivial:

redis_config = { 
  url: Chamber.dig!(:redis, :url), 
  # Heroku uses self-signed certs, disable CA validation
  ssl_params: { verify_mode: OpenSSL::SSL::VERIFY_NONE } 
}

Sidekiq.configure_server { |config| config.redis = redis_config }
Sidekiq.configure_client { |config| config.redis = redis_config }

I'm worried if the log output means Sidekiq tries to talk to redis when it is not supposed to.

[mperham]

That log output happens when Sidekiq first tries to connect to Redis. If you can get the full backtrace from that log (by adding raise after that log line), we can determine why it's connecting and possibly fix it.

[timon]

I tried that, and it lead me to at_exit hook in Sidekiq::ReliableClient:

$ RAILS_ENV=test be rake db:test:prepare
2023-03-20T09:34:31.176Z pid=98107 tid=1ij INFO: Sidekiq 7.0.7 connecting to Redis with options {:size=>5, :pool_name=>"internal", :url=>nil}
2023-03-20T09:34:31.176Z pid=98107 tid=1ij INFO: Caused by:
  (Rails.root)/vendor/bundle/ruby/2.7.0/gems/sidekiq-7.0.7/lib/sidekiq/config.rb:132:in `new_redis_pool'
  (Rails.root)/vendor/bundle/ruby/2.7.0/gems/sidekiq-7.0.7/lib/sidekiq/config.rb:126:in `local_redis_pool'
  (Rails.root)/vendor/bundle/ruby/2.7.0/gems/sidekiq-7.0.7/lib/sidekiq/config.rb:120:in `redis_pool'
  (Rails.root)/vendor/bundle/ruby/2.7.0/gems/sidekiq-7.0.7/lib/sidekiq/client.rb:55:in `initialize'
  (Rails.root)/vendor/bundle/ruby/2.7.0/gems/sidekiq-pro-7.0.8/lib/sidekiq/pro/push.rb:29:in `new'
  (Rails.root)/vendor/bundle/ruby/2.7.0/gems/sidekiq-pro-7.0.8/lib/sidekiq/pro/push.rb:29:in `block in <module:ReliableClient>'

[mperham]

thanks, that'll be fixed in the next Pro release.