forked from pool/python-celery
- Update to 3.0.19:
- Now depends on billiard 2.7.3.28
- A Python 3 related fix managed to disable the deadlock fix
announced in 3.0.18.
Tests have been added to make sure this does not happen again.
- Task retry policy: Default max_retries is now 3.
This ensures clients will not be hanging while the broker is down.
You can set a longer retry for the worker by
using the celeryd_after_setup signal:
from celery.signals import celeryd_after_setup
@celeryd_after_setup.connect
def configure_worker(instance, conf, **kwargs):
conf.CELERY_TASK_PUBLISH_RETRY_POLICY = {
'max_retries': 100,
'interval_start': 0,
'interval_max': 1,
'interval_step': 0.2,
}
- Worker: Will now properly display message body in error messages
even if the body is a buffer instance.
- 3.0.18 broke the MongoDB result backend (Issue #1303).
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-celery?expand=0&rev=79
This commit is contained in:
committed by
Git OBS Bridge
parent
1d9340b693
commit
af5b4dc9a5
@@ -1,3 +1,29 @@
|
||||
-------------------------------------------------------------------
|
||||
Tue Apr 30 19:34:54 UTC 2013 - alexandre@exatati.com.br
|
||||
|
||||
- Update to 3.0.19:
|
||||
- Now depends on billiard 2.7.3.28
|
||||
- A Python 3 related fix managed to disable the deadlock fix
|
||||
announced in 3.0.18.
|
||||
Tests have been added to make sure this does not happen again.
|
||||
- Task retry policy: Default max_retries is now 3.
|
||||
This ensures clients will not be hanging while the broker is down.
|
||||
You can set a longer retry for the worker by
|
||||
using the celeryd_after_setup signal:
|
||||
from celery.signals import celeryd_after_setup
|
||||
|
||||
@celeryd_after_setup.connect
|
||||
def configure_worker(instance, conf, **kwargs):
|
||||
conf.CELERY_TASK_PUBLISH_RETRY_POLICY = {
|
||||
'max_retries': 100,
|
||||
'interval_start': 0,
|
||||
'interval_max': 1,
|
||||
'interval_step': 0.2,
|
||||
}
|
||||
- Worker: Will now properly display message body in error messages
|
||||
even if the body is a buffer instance.
|
||||
- 3.0.18 broke the MongoDB result backend (Issue #1303).
|
||||
|
||||
-------------------------------------------------------------------
|
||||
Fri Apr 12 17:52:35 UTC 2013 - alexandre@exatati.com.br
|
||||
|
||||
|
||||
Reference in New Issue
Block a user