Liveness probe failing when connection pool is full
Issue
Liveness Probe is failing when the connection poolis becoming full. Liveness probe failure triggers a pod restart, although the pod was still fully healthy.
This can be very annoying in case of long running transaction, as the long running transaction will get cancelled in the middle.
The liveness probe should not trigger a pod when the system is healthy and responding, even if the connection is full
Environment
- Red Hat Single Sign-On (RH SSO)
- 7.6
- Openshift
- Connection pool
- Liveness Probe
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
