This repository has been archived by the owner on Jul 27, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 17
Two Readiness checks #2
Comments
@gdams can you take a look? |
gdams
pushed a commit
to gdams/cloud-health
that referenced
this issue
Nov 30, 2018
Fixes an issue where you have two readiness checks (the first not ready and the second being ready. This now keep the readiness set as `STARTING` rather than `UP` Issue number: CloudNativeJS/cloud-health-connect#2
gdams
pushed a commit
to CloudNativeJS/cloud-health
that referenced
this issue
Dec 3, 2018
* Fix issue with Two Readiness checks Fixes an issue where you have two readiness checks (the first not ready and the second being ready. This now keep the readiness set as `STARTING` rather than `UP` Issue number: CloudNativeJS/cloud-health-connect#2 * add more coverage * add coveralls as dev dep
gdams
pushed a commit
to gdams/cloud-health-connect
that referenced
this issue
Dec 3, 2018
fixed in |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I originally posted this in cloud-health, but have moved it here.
I registered two readiness checks (one to check a valid mongodb connection, one to check a valid redis connection). If I call resolve on the second (redis), but not the first (mongo), my status is still UP. Shouldn't it be still STARTING? If i hit the /ready api, the returned checks array is emtpy.
If I swap out registerReadinessCheck for registerLIvenessCheck both the /ready and /health routes return both checks, but the states are still off.
Here is the code:
I initialize as follows:
Create some readiness checks:
And later on I do the following:
In summary my questions are:
Thanks,
Jas
The text was updated successfully, but these errors were encountered: