-
Notifications
You must be signed in to change notification settings - Fork 20
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
Bug: django q probe times out on kubernetes #5263
Comments
MichaelAkvo
added a commit
that referenced
this issue
Mar 22, 2023
Running django-admin commands using ./manage.py takes about 6 seconds to startup, sometimes longer. In order to have faster feedback for probes, a local HTTP server is started using `./manage.py django_q_probettp` Its only function is to return the status of the local cluster. Additionally, the worker was forgotten in the training-env, so it's now added there.
5 tasks
MichaelAkvo
added a commit
that referenced
this issue
Mar 22, 2023
Running django-admin commands using ./manage.py takes about 6 seconds to startup, sometimes longer. In order to have faster feedback for probes, a local HTTP server is started using `./manage.py django_q_probettp` Its only function is to return the status of the local cluster. Additionally, the worker was forgotten in the training-env, so it's now added there.
MichaelAkvo
added a commit
that referenced
this issue
Mar 22, 2023
Running django-admin commands using ./manage.py takes about 6 seconds to startup, sometimes longer. In order to have faster feedback for probes, a local HTTP server is started using `./manage.py django_q_probettp` Its only function is to return the status of the local cluster. Additionally, the worker was forgotten in the training-env, so it's now added there.
MichaelAkvo
added a commit
that referenced
this issue
Mar 22, 2023
The `worker` service took a long time to start after the `web` service, because the interval for the `web` service was really long. The interval was so high to cope with the long startup time of the `web` service, but the config option for that is `start_period` not `interval`.
MichaelAkvo
added a commit
that referenced
this issue
Mar 22, 2023
Running django-admin commands using ./manage.py takes about 6 seconds to startup, sometimes longer. In order to have faster feedback for probes, a local HTTP server is started using `./manage.py django_q_probettp` Its only function is to return the status of the local cluster. Additionally, the worker was forgotten in the training-env, so it's now added there.
MichaelAkvo
added a commit
that referenced
this issue
Mar 22, 2023
The `worker` service took a long time to start after the `web` service, because the interval for the `web` service was really long. The interval was so high to cope with the long startup time of the `web` service, but the config option for that is `start_period` not `interval`.
zuhdil
added a commit
that referenced
this issue
Mar 27, 2023
…on-kubernetes [#5263] Provide localhost server for django-q probe
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What were you doing?
Starting up the application on kubernetes.
What should've happened?
The readiness probe shouldn't time out so frequently.
My environment
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: