Optimize OpenShift healthchecks #297

New issue

Closed

opened 2026-03-06 10:38:43 +00:00 by jgroman · 3 comments

jgroman commented

2026-03-06 10:38:43 +00:00

Owner

OpenShift checks blockerbugs pod service health using Readiness and Liveness probes which both independently hit app main page at 5 sec period resulting in main page refreshes every 2.5 sec or so. This causes unnecessary main page traffic and may have negative impact on app response delay.
We should review healtcheck period lengths and probably make those longer and also create a special endpoint dedicated for those health checks which would just do a simple and fast db query (like retrieving db version) thus reducing server and db load.

OpenShift checks blockerbugs pod service health using Readiness and Liveness probes which both independently hit app main page at 5 sec period resulting in main page refreshes every 2.5 sec or so. This causes unnecessary main page traffic and may have negative impact on app response delay. We should review healtcheck period lengths and probably make those longer and also create a special endpoint dedicated for those health checks which would just do a simple and fast db query (like retrieving db version) thus reducing server and db load.

kparal commented

2026-03-11 12:25:01 +00:00

Owner

This seems to be partially implemented in #299 , IIUIC?

@main.route('/_health')
			def get_health_check():
			    """Endpoint for processing health check requests from loadbalancers etc."""
			    response = make_response('OK')
			    response.mimetype = 'text/plain'
			    return response

This seems to be partially implemented in #299 , IIUIC? ``` @main.route('/_health') def get_health_check(): """Endpoint for processing health check requests from loadbalancers etc.""" response = make_response('OK') response.mimetype = 'text/plain' return response ```