A backend that is slow for a moment leaves the service ready #3
Loading…
Reference in a new issue
No description provided.
Delete branch "main"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The readiness probe listed in the store while the probe waited, and the probe has a deadline of its own (one second
in Kubernetes unless told otherwise). A store that is slow is slow for every replica at once: in a region, about one
probe in twenty ran into the deadline in both replicas in the same minutes, and once both left the service in the
same seconds, although each would have served its requests, only slowly.
The store is now asked beside the probe, once at a time. The probe waits half a second for it and otherwise answers
with what was last found, as long as that is no older than a minute. A store that fails is reported at once, one
that does not answer within 15 seconds counts as not reached, and one that never answered is not ready. The check is
one object for the life of the service, since a check made anew for every probe remembers nothing.
Co-Authored-By: Claude Fable 5.2 noreply@anthropic.com