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
We are considering moving to sneakers and advanced-sneakers-activejob from sidekiq. One thing that I get with sidekiq is the ability to see if workers are running on some background task. Sidekiq::Workers.new.size > 0
We can write our own way of registering and checking, but I was wondering if sneakers had something that I have not noticed or if you would recommend another way to get to the information?
The text was updated successfully, but these errors were encountered:
OK, I have come to the conclusion that barring something catastrophic (like the workers have all crashed or are not running), the fact that there is something in the queue implies some or all tasks are running IF the queue is a must ack queue. The way that advanced-sneakers-activejob is built, it wraps the transactions, yields and then acks, so even if I err out, I am going to get an ack. I am good to go.
We are considering moving to sneakers and advanced-sneakers-activejob from sidekiq. One thing that I get with sidekiq is the ability to see if workers are running on some background task.
Sidekiq::Workers.new.size > 0
We can write our own way of registering and checking, but I was wondering if sneakers had something that I have not noticed or if you would recommend another way to get to the information?
The text was updated successfully, but these errors were encountered: