| Age | Commit message (Collapse) | Author |
|---|
|
Also only sleep between fetches if we couldn't find a job because
the queue was empty.
|
|
|
|
The new approach uses the redis gems timeout functionality
and ensures we never return a null-job. Instead we timeout
and repeat with a stalling-sleep in the way.
This closes #9553.
|
|
|
|
We now set the queue-address via $QUEUE_ADDRESS, otherwise
we default to localhost. This works for both redis & beanstalkd.
|
|
Now that we've moved to using redis by default the handling of queue-flushing
needs to change. We can simply get rid of the busy-wait and run a redis
"del" operation.
With that in mind we've moved the flushing logic to our queue abstraction
layer, and simplified our queue-helper script.
|
|
|
|
This means we can queue/dequeue to either Redis or Beanstalkd.
|
|
This is not-yet used, but it will-be shortly. The intention is
that we can seamlessly swap out the queue implemention in the
near future so that we'll be able to use Redis.
|
|
|
|
|
