Instead of relying on a one-time blocking check with no reponse timeout, we now issue a blocking request with a 5 second idle time limit. If it fails, the store will still be created, but it will go into the same asyncronous re-evaluation loop as when performance is below the acceptable threshold and re-evaluate at 30 second intervals until both:
- Health is Ok
- Performance criteria (if any has been configured and is in use) is met
At which point it is activated. Health checks have been changed from the health/status endpoint to health/ready because we don't want to act if the server is running but not ready for requests (eg: during the time when it may be wiping data during a schema change.
The overall goal is that we don't force the entire session to execute without zenserver if zenserver was not ready at startup.
#rb Devin.Doucette
[CL 30295095 by zousar shaker in ue5-main branch]
ae71242205