-
Notifications
You must be signed in to change notification settings - Fork 12
Readiness liveliness probe design
José Bonnet edited this page Feb 26, 2019
·
2 revisions
This wiki page summarises the design of the Readiness/Liveness probes in the tng-api-gtw component. For its usage, please check here.
...
- Readiness: probe to check if the component is ready to receive requests;
- Liveliness: probe to check if the component is alive (i.e., can continue to receive requests).
Given the REST APIs we're using, the same endpoint can work for both kinds of checks: calls to check
- readiness will fail until the component is ready to accept the kind of requests it was designed to accept;
- liveliness will succeed, unless the component is not ready to accept the kind of requests it was designed to accept;