-
Given that:
I have a scenario where I want lock args to effectively return a random result at runtime, but I want it to lock uniquely based on the job's arguments at queue-time. In other words I want a neatly structured set of unique jobs in the queue, but when pulled off the queue to run, I want them to randomly succeed or fail, and I need this to happen via the locking mechanism. Is it possible to differentiate between queue-time and execution-time within the |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Fundamentally what I was looking for was concurrency limiting, falling back on the retries to simulate a concurrency limit. I think I can accomplish what I want with https://github.com/ixti/sidekiq-throttled instead. |
Beta Was this translation helpful? Give feedback.
Fundamentally what I was looking for was concurrency limiting, falling back on the retries to simulate a concurrency limit. I think I can accomplish what I want with https://github.com/ixti/sidekiq-throttled instead.