A 90‑Minute Spike for Health Checks That Can Fail
Описание и применение
Спайк длительностью 90 минут позволяет убедиться, что эндпоинт /ready возвращает 503 при падении хранилища и 200 после восстановления, предотвращая маршрутизацию трафика к неработающим сервисам.
Задача
Health‑check endpoints often return 200 even when critical dependencies are down, causing load balancers to route traffic to unhealthy services.
Результат
After a 90‑minute spike, the service correctly reports 503 on /ready when the store is down and recovers to 200 once the store is available, preventing traffic to unhealthy instances.
Рабочий процесс
- Set up a store stub that raises DependencyDown when STORE_DOWN=1
- Create a baseline handler that always returns 200 for /health and /ready
- Write kill tests that start the app with STORE_DOWN=1 and verify /ready stays 200
- Run tests for 90 minutes, cycling through constrained agent passes and repair passes
- Stop the spike after 90 minutes and document the ship‑or‑kill decision
Доказательства
Unconstrained coding agents skip checks in health routes. They return 200 because the process started.
Kill if /ready stays 2xx while a required store is down.
- Дата записи: 2026-09-13T11:03:34.667Z