Mike Perham
3eb6ad457c
Explicitly test false to avoid warning on Ruby 2.0, fixes #869
2013-04-24 10:53:02 -07:00
Mike Perham
e7eca11811
I dont think we want to skip retry, #377
2013-03-26 23:00:18 -07:00
Mike Perham
cfae522adf
Raise within any workers which haven't finished within the hard timeout, fixes #377
2013-03-26 22:56:49 -07:00
Mike Perham
879995dd08
actually test exhausted feature
2013-03-21 14:37:41 -07:00
Mike Perham
c62f59e62a
Merge pull request #780 from EasyGive/master
...
Hook to process events after a job fails all retries
2013-03-21 12:51:11 -07:00
James Kassemi
2241e659f6
Documentation update 'exhausted' to 'retries_exhausted'
2013-03-21 13:49:05 -06:00
James Kassemi
5824857b59
'exhausted' changed to 'retries_exhausted'
...
Additionally, any errors raised during retries_exhausted hook
are logged and dropped before resuming original control flow.
2013-03-21 12:16:07 -06:00
lulalala
e649006109
Makes retry time calculation easier to monkey-patch by changing it from
...
a constant proc to a method.
2013-03-20 16:14:10 +08:00
James Kassemi
172434d459
Call 'exhausted' worker method after retries
...
When the maximum number of retries is hit and the message is about
to be thrown away, give the option of allowing the worker to say
goodbye by defining an 'exhausted' method on the worker.
2013-03-18 15:20:28 -06:00
Ryan Lower
b199d37efd
Allow specification of retry_queue in sidekiq_options
2013-01-15 17:28:52 -08:00
Mike Perham
1d85edef1b
Fix retry off by one, #512
2012-11-09 21:36:40 -08:00
Preston Marshall
b08696bd50
Added a splay to the delay time for retried jobs. [ Fixes #480 ]
...
The amount of splay increases as the number of failures increases. The maximum amount of splay is equal to 30 * (the number of times the job has failed, plus 1). For the default max retries setting, the maximum splay would be 780 seconds.
2012-10-30 16:56:50 -05:00
Noah Davis
bc1e38f85a
use 'retry' option to customize max retry attempts
...
e.g.
{ 'class' => 'HardWorker', 'args' => [1, 2, 'foo'], 'retry' => 5 }
Addresses Issue #313
2012-10-17 18:58:07 -04:00
Mike Perham
1d3401afd6
Fix a few more Exception leaks
2012-08-29 20:20:20 -07:00
Mike Perham
2c4be4cada
Scheduled jobs! Bump to 2.0.0.
...
Performs can now be scheduled at arbitrary points in the future.
2012-05-25 20:21:42 -07:00
Mike Perham
e65efd5f0a
Implement optional backtrace storage [ #155 ]
2012-04-27 20:25:46 -07:00
Erik Michaels-Ober
5eb8d397f0
Refactor to use Sidekiq.dump_json and Sidekiq.load_json
...
These methods perform MultiJson feature detection and can be removed
after this library's MultiJson dependency is upgraded to ~> 2.0.
2012-04-22 14:02:35 -07:00
Erik Michaels-Ober
68c725e47b
Let's try this again...
...
Use `Object#respond_to?` to determine which MultiJson API to use.
2012-04-22 13:46:00 -07:00
Mike Perham
9c6b967029
Revert "Use MultiJson APIs introduced in version 1.3 to suppress deprecation warnings"
...
Breaks Rails 3.2 and lower
This reverts commit 9c6d5623a1
2012-04-18 14:57:24 -07:00
Erik Michaels-Ober
9c6d5623a1
Use MultiJson APIs introduced in version 1.3 to suppress deprecation warnings
2012-04-18 10:51:25 -07:00
Mike Perham
2080412119
Client API update:
...
- Add API for configuring options per Worker class
- Removed the Client API issues preventing it working on Ruby 1.8
- Cleanups to various APIs for upcoming 1.0 release.
2012-04-01 19:53:45 -07:00
Mike Perham
e38a3d785a
Auto failure retry now working!
2012-03-17 23:04:31 -07:00
Mike Perham
08fd2b9cf5
HOT new automatic retry feature. Needs testing.
2012-03-17 17:59:46 -07:00
