[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Liveness vs Readiness probes

A readiness probe will ensure traffic won't be sent to a non ready container.  But if that container is in a bad state such that it will never be "ready", it's just wasting resources (and if it's your only container (replica count =1) then your application will be unavailable and stay that way).

A failing liveness probe will cause a restart of a badly behaving container, which (hopefully) will get it back to a state where it can pass a readiness probe and begins serving traffic again.
So yes, you likely still want a liveness probe.

Ben Parees | OpenShift

On Nov 22, 2015 10:41, "Philippe Lafoucrière" <philippe lafoucriere tech-angels com> wrote:

Regarding the doc https://docs.openshift.com/enterprise/3.0/dev_guide/application_health.html
I'm not 100% sure if I need to add a liveness probe when I already have a readiness probe (on a http port) configured. Can someone enlighten me on this please?

Also, weird thing: If I edit a DC to add a probe (live or ready), I get a:
"Edit cancelled, no changes made."
message, and the dc is indeed not changed. 


Philippe Lafoucrière - CEO
main : +33 (0) 970 444 643
mobile CA: +1 (581) 986-7540

users mailing list
users lists openshift redhat com

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]