Skip to content
This repository was archived by the owner on Feb 16, 2023. It is now read-only.

Conversation

@evilsidekick293
Copy link

see #1469

This is especially interesting for the combination of a large file and a weak hardware setup.

- defaults to 1800 seconds
- can be configured through environment for systems with weaker CPUs
- description added to documentation
@evilsidekick293 evilsidekick293 force-pushed the feature/worker-timeout-fix branch from 6986b3b to f9fe146 Compare December 6, 2021 08:29
@nbently
Copy link

nbently commented Jan 6, 2022

Thanks for digging into this, really helped me & my weak hardware 😁. Django Q doesn't like it when the timeout value is set higher than the retry value.

/usr/local/lib/python3.9/site-packages/django_q/conf.py:139: UserWarning: Retry and timeout are misconfigured. Set retry larger than timeout, 
        failure to do so will cause the tasks to be retriggered before completion. 
        See https://django-q.readthedocs.io/en/latest/configure.html#retry for details.

Might want to just amend the PR so the PAPERLESS_WORKER_TIMEOUT value sets both the retry & timeout values in the q cluster (which is what I did in my fork).

@evilsidekick293 evilsidekick293 closed this by deleting the head repository Nov 6, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants