backburner
backburner copied to clipboard
nesquena
Simple and reliable beanstalkd job queue for ruby
For some unknown reason this error is occurring continuously, when I switched my worker type from simple to threadsonfork. It is running on centos 7. There is a possible suspicion...
Hello there! I've been using this gem to enqueue jobs for a long time as suggested in the docs (with God monitoring); nonetheless, I've been noticing that every time the...
The docs for hooks give a couple examples for an `on_failure_bury` method that goes on to call `self.bury`. The problem is that `self.bury` isn't a method and implementing a hook...
Hello, I'm trying to run my worker in ThreadsOnFork mode, with a number of thread of 1 for now (will increase in the future), with multiple queue, but only the...
We have long running jobs and need to be able to touch them. I tried something with a thread checking if the job is timed out and not using a...
https://github.com/beanstalkd/beanstalkd/pull/150 merged ``` beanstalkd://%2Ftmp%2Fbeanstalkd.sock (Backburner::Connection::BadURL) ```
Why we need to create new connection every time we enqueue a job? https://github.com/nesquena/backburner/blob/master/lib/backburner/worker.rb#L39 It leads to a very huge number of connections. In my case it can even exhaust...
As of today, [Datadog does not support Backburner](https://docs.datadoghq.com/tracing/setup/ruby/#library-compatibility). What is the recommended approach to setup the monitoring hooks for backburner in Datadog?
Currently the max_job_retries and retry_delay settings apply to every tube that backburner watches. For some tubes that I'm processing I'd like a large number of retries for, while for others...
Looking at the Backburner README doc: `queue_respond_timeout 300 # number of seconds before job times out, 0 to avoid timeout` Looking at the Beanstalk [protocol doc](https://raw.githubusercontent.com/kr/beanstalkd/master/doc/protocol.txt): ``` The minimum ttr...
