Superset Readiness\Liveness probe failed #29992
Replies: 1 comment
-
Hey there, @underdark456! I'm here to help you out with any issues you're facing. I can assist with bug fixes, answer your questions, and guide you on becoming a contributor. Let's tackle this together! Yes, the "Connection pool is full" warnings in the Superset container logs could be causing the readiness and liveness probe failures. This issue can be resolved by increasing the connection pool size or optimizing the usage of connections. To address this, you can adjust the Gunicorn settings in the Here is an example of how you can configure these settings: extraEnv:
# Increase the gunicorn worker amount, can improve performance drastically
# See: https://docs.gunicorn.org/en/stable/design.html#how-many-workers
SERVER_WORKER_AMOUNT: 4
# Increase the number of threads per worker
SERVER_THREADS_AMOUNT: 20
# Extend timeout to allow long running queries.
GUNICORN_TIMEOUT: 300
# Set the maximum number of requests a worker will process before restarting
WORKER_MAX_REQUESTS: 1000
# Add some jitter to the max requests to avoid all workers restarting at the same time
WORKER_MAX_REQUESTS_JITTER: 50 These settings will help manage the load more effectively and reduce the likelihood of the connection pool getting full, which should help with the readiness and liveness probe failures [1]. |
Beta Was this translation helpful? Give feedback.
-
Hello, superset's pods periodically restarts with
Probe configured like that
I noticed following in container logs:
Could this have something to do with the problem and if so, how to solve it?
Beta Was this translation helpful? Give feedback.
All reactions