README.md in backburner-1.4.1 vs README.md in backburner-1.5.0
- old
+ new
@@ -1,6 +1,6 @@
-# Backburner
+# Backburner [](https://travis-ci.org/nesquena/backburner)
Backburner is a [beanstalkd](http://kr.github.com/beanstalkd/)-powered job queue that can handle a very high volume of jobs.
You create background jobs and place them on multiple work queues to be processed later.
Processing background jobs reliably has never been easier than with beanstalkd and Backburner. This gem works with any ruby-based
@@ -32,11 +32,11 @@
## Why Beanstalk?
Illya has an excellent blog post
[Scalable Work Queues with Beanstalk](http://www.igvita.com/2010/05/20/scalable-work-queues-with-beanstalk/) and
-Adam Wiggins posted [an excellent comparison](http://adam.heroku.com/past/2010/4/24/beanstalk_a_simple_and_fast_queueing_backend/).
+Adam Wiggins posted [an excellent comparison](http://adam.herokuapp.com/past/2010/4/24/beanstalk_a_simple_and_fast_queueing_backend/).
You will quickly see that **beanstalkd** is an underrated but incredible project that is extremely well-suited as a job queue.
Significantly better suited for this task than Redis or a database. Beanstalk is a simple,
and a very fast work queue service rolled into a single binary - it is the memcached of work queues.
Originally built to power the backend for the 'Causes' Facebook app, it is a mature and production ready open source project.
@@ -510,9 +510,12 @@
config.on_error = lambda { |ex| Airbrake.notify(ex) }
end
```
Now all backburner queue errors will appear on airbrake for deeper inspection.
+
+If you wish to retry a job without logging an error (for example when handling transient issues in a cloud or service oriented environment),
+simply raise a `Backburner::Job::RetryJob` error.
### Logging
Logging in backburner is rather simple. When a job is run, the log records that. When a job
fails, the log records that. When any exceptions occur during processing, the log records that.