sidekiq-throttled
sidekiq-throttled copied to clipboard
ixti
Concurrency and rate-limit throttling for Sidekiq
`versions` sidekiq (6.5.5) sidekiq-throttled (0.16.2) redis (4.8.0) ``` Passing the timeout as a positional argument is deprecated, it should be passed as a keyword argument: redis.brpop("queue:mailers", "queue:api_call", "queue:scheduled", "queue:searchkick", "queue:active_storage_analysis",...
It's possible to throttle queue by using shared throttling key, but that causes jobs to be pushed back to the end of the queue. It would be nice to have...
Allow `Config#cooldown_period` and `Config#cooldown_threshold` to be specified as Proc: ``` ruby Sidekiq::Throttled.configure do |c| c.cooldown_period = lambda do |queue_name| queue_name == "default" ? 2.0 : 10.0 end c.cooldown_threshold = lambda...
This adds support for setting the `requeue_strategy` for a job, to specify what we should do with throttled jobs. The default is `:enqueue`, which is the current behavior: re-add it...
Is it possible to set multiple throttle option like: 5 per 1 minute 100 per 1 hour 1000 per 1 day All of them for the same worker.
We were using version `1.0.0.alpha.1` with Sidekiq 5.5.9 when we noticed a strange issue where we would get many copies of jobs in our retry queue. We upgraded sidekiq to...
I'm currently seeing batches of jobs that are configured to throttle dynamically get stuck when the throttle configuration changes. For example, here's my throttle config... ```rb sidekiq_throttle( concurrency: { limit:...
Hopefully a quick question to clarify expected behaviour. We are seeing jobs waiting in the Enqueued state due to configured rate limit throttling (expected). However, there may be other jobs...
My goal is to allow at least 100 jobs per account with a maximum of 600 concurrent jobs in a minute. However, I would like this to be dynamic based...
