-
Notifications
You must be signed in to change notification settings - Fork 7
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
Provide health check for Docker image #550
Comments
Doesn't this solve the |
Yes, I'm implementing it on the "system" endpoint so we don't have to rely on APIs that could be disabled at any time. I will also detect the situations when queues are full and requests are rejected, also when GC cannot free memory and the system will crash due to insufficient memory, and also when there are a lot of internal errors that might signal some problem. This is not covered by our "liveness" probes in the GQL / REST APIs. |
We should also prepare readiness probe. See Kubernetes documentation |
Added link between readiness and liveness probe. Allow to configure system API port and start delay in Dockerfile using environment variables.
Fixed work with service loader and probe instantiation.
To reliably run evitaDB on production systems, we need to provide a health check for the Docker container. The container should be healthy if no OutOfMemoryError occurred and the endpoint responds within 2s with 2 retries.
The text was updated successfully, but these errors were encountered: