I created some workers with coffee reské and tried to look at the workers using the ruby version of resque-web, and saw only flashing workers.
I noticed that the coffee rusk was hanging when it stopped. Is this intended behavior? This made it so that only iridescent intermittent workers appeared on the resque network, and they always had a waiting status when they appeared, although that was when they were being processed.
Am I doing this wrong or is there a suggested way to monitor work queues?
Also, is there a way to clear inactive orphaned work keys in redis if the workflow failed and didn’t make a graceful untrack on exit?
MonkeyBonkey
source share