-
-
Notifications
You must be signed in to change notification settings - Fork 285
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
How to increase timeout of failed jobs #455
Comments
Are you getting the queue using |
Hi @selwin. Do you mean when I requeue the failed jobs? I don't do it programmatically. I use django admin action: |
No, I meant when you're enqueueing the job originally. |
I'm using method decorator:
so yes, I presume it is using |
Yeah, so I think that should work. Are your settings.py configured correctly? Alternatively you can also do |
When I increase the timeout in the settings, it is applied to all new delayed jobs successfully. But it is not applied to the requeued failed jobs. Old timeout value is used. |
Ah ok. Then what’s needed is a feature that allows you to update job.timeout prior to requeueing it.
Unfortunately this feature is not in DjangoRQ yet. If you want, I’ll be happy to accept a PR for this.
… On Nov 30, 2020, at 3:54 PM, Erik Telepovský ***@***.***> wrote:
When I increase the timeout in the settings, it is applied to all new delayed jobs successfully. But it is not applied to the requeued failed jobs. Old timeout value is used.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I can look into it. Can you guide me where to start? |
Create an |
And what about automatic timeout update according to the current settings when job is requeued? |
It won't be automated, since the |
I created a PR #458 |
Hello. Is there a way how to change/increase timeout of failed jobs?
My jobs fail with exception:
so I increased the
DEFAULT_TIMEOUT
inRQ_QUEUES
setting, but every time I requeue failed jobs, the new setting is ignored and and is used previous timeout value.The text was updated successfully, but these errors were encountered: