You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have received a lot of questions about how to throttle jobs using sidekiq-unique-jobs. After searching for throttling sidekiq jobs I ended up with sidekiq-throttler. Which seams like a pretty straight forward way of doing what most people want with the uniqueness expiration.
Is throttling jobs something that should exist in the sidekiq-unique-jobs gem or should we remove all expiration completely and tell people to use sidekiq-throttler instead?
The reason for clearing jobs in the first place was that some jobs never got cleared ever so no new such jobs could be scheduled however in a recent release of sidekiq @mperham added clearing of stale jobs after 60 minutes meaning we could only ever keep jobs for 60 minutes or we would have to turn to another solution. I am still undecided on how to proceed here so any suggestions you have are greatly appreciated.
The text was updated successfully, but these errors were encountered:
I have received a lot of questions about how to throttle jobs using
sidekiq-unique-jobs
. After searching for throttling sidekiq jobs I ended up with sidekiq-throttler. Which seams like a pretty straight forward way of doing what most people want with the uniqueness expiration.Is throttling jobs something that should exist in the
sidekiq-unique-jobs
gem or should we remove all expiration completely and tell people to use sidekiq-throttler instead?The reason for clearing jobs in the first place was that some jobs never got cleared ever so no new such jobs could be scheduled however in a recent release of sidekiq @mperham added clearing of stale jobs after 60 minutes meaning we could only ever keep jobs for 60 minutes or we would have to turn to another solution. I am still undecided on how to proceed here so any suggestions you have are greatly appreciated.
The text was updated successfully, but these errors were encountered: