Sidekiq: Redesign reliable_fetch

Created on 27 Jul 2016  路  4Comments  路  Source: mperham/sidekiq

  • Remove the hostname/index hack.
  • Keep the O(1) performance.

Processes should register a private queue upon startup, associated with their heartbeat. On startup, each process should check the validity of each process heartbeat. If invalid, any private queue contents should be re-enqueued.

ETA: September.

Most helpful comment

Coming in Sidekiq Pro 3.4.0.

https://github.com/mperham/sidekiq/wiki/Pro-Reliability-Server#super_fetch

Sidekiq.configure_server do |config|
  config.super_fetch!
end

super_fetch! will become an alias for reliable_fetch! in Sidekiq Pro 4.0 so that hostname/index issues become a thing of the past.

All 4 comments

Coming in Sidekiq Pro 3.4.0.

https://github.com/mperham/sidekiq/wiki/Pro-Reliability-Server#super_fetch

Sidekiq.configure_server do |config|
  config.super_fetch!
end

super_fetch! will become an alias for reliable_fetch! in Sidekiq Pro 4.0 so that hostname/index issues become a thing of the past.

Hi @mperham, any idea about the release date of super_fetch!?

Twoish weeks.

:ok_hand:

Was this page helpful?
0 / 5 - 0 ratings