-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle celery errors by re-running async task #14
Handle celery errors by re-running async task #14
Conversation
return | ||
except kombu.exceptions.OperationalError as err: | ||
logger.warn('kombu.exceptions.OperationalError') | ||
pass |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we log how many attempts we're at and if we hit 3?
except kombu.exceptions.OperationalError as err: | ||
logger.warn('kombu.exceptions.OperationalError (attempt: %s)', attempt) | ||
if attempt >= MAX_ATTEMPTS - 1: | ||
raise err |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to have the option to fall back to running the task synchronously, perhaps controlled by a django setting, or else an option in the DeferrableTask
decorator
I like |
@dshafer so demanding ;) Should be satisfied by the most recent commit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lol
No description provided.