Sidekiq throttler works by scheduling anything beyond a certain threshold in the next window of time as defined by a period option defined in sidekiq configs.
However, scheduled jobs (when unscheduled) fail to go to the correct 'priority' queue & instead go to the default queue.
I think that the correct way to handle this is to change the queue on the job before calling 'client_push' in worker_ext.rb, but I need to look more closely at it. I'm reporting the issue to invite anyone else to do the same.
There's an interaction issue with sidekiq-throttler.
Sidekiq throttler works by scheduling anything beyond a certain threshold in the next window of time as defined by a period option defined in sidekiq configs.
However, scheduled jobs (when unscheduled) fail to go to the correct 'priority' queue & instead go to the default queue.
I think that the correct way to handle this is to change the queue on the job before calling 'client_push' in worker_ext.rb, but I need to look more closely at it. I'm reporting the issue to invite anyone else to do the same.