kue-scheduler
kue-scheduler copied to clipboard
lykmapipo
A job scheduler utility for kue, backed by redis and built for node.js
Hi, I'm running into a problem where if I have two node servers connecting to the same Redis try to use 'every' to set up recurring execution of the same...
I have used kue-scheduler in production since its birth. I will appreciate if we can review the codes and come up with milestones to cleanup its internals. I will appreciate...
1. Use appropriate data structures for every scenarion 2. Avoid JSON.stringify whenever possible to store data as a string
After reviewing the codes, I have seen errors just thrown and handled independently of the queue instance. I think it will be proper if all errors can be propagated to...
This will solve a situation when someone wants to cleanup all jobs and restart a fresh
I have set up kue to run with the [Cluster](https://nodejs.org/api/cluster.html) module, which spawns a child process of `kue` for every CPU core available.. When the scheduler inserts the `every` keys...
I have used a queue.schedule(when, job) in a loop and in this loop I want to send data to every schedule. How I can manage this?
Just a heads up that there is active development on kue v1. It doesn't look like there will be very many changes that will break scheduler or kue-unique directly, but...
