Liveness and readiness probes answer different questions
Liveness decides whether Kubernetes restarts a container. Readiness decides whether it gets traffic. Wiring one health check to both turns a slow dependency into a restart storm.
Topic · 8 stories
8 stories tagged reliability on AI Tamer, newest first.
Liveness decides whether Kubernetes restarts a container. Readiness decides whether it gets traffic. Wiring one health check to both turns a slow dependency into a restart storm.
An agent that retries a failing tool call immediately, at every layer, can turn a short blip into an outage. Backoff, jitter, retry limits and which errors to retry at all.
One missing IP fragment can erase a whole UDP datagram. Path MTU discovery and application-sized messages help voice systems avoid that failure mode.
A burst of voice worker errors can exceed journald’s per-service limit. Learn how its interval, burst and disk rules affect what an incident log can prove.
stale-while-revalidate and stale-if-error permit different kinds of bounded staleness. Their windows start after freshness ends, and each trades current data for a specific benefit.
A model can request several functions in one turn. The application must decide how to schedule them, match their results, and handle partial failure.
A Collector can accept spans while its exporter falls behind. Its internal metrics show where delivery slows, where data is refused, and when loss becomes likely.
An agent that reads documents and writes a summary can hand you a finished document that is somehow empty. This is the gap, and it has two honest fixes.