---
title: "Comment by Mike Dabydeen on \"Chaos drills for a streaming system: what restarting and killing every component taught me\" | Hashnode"
description: "For \"recovered\" I'd keep your on-time-window rule and change what you report: a spread over repeated kills, because where the kill lands in the commit cycle dec"
url: "https://hashnode.com/posts/kafka-chaos-testing-restart-vs-kill/6afc48e1485f929a3f847aeb/comment/6afd97034300b22e5f05ab85"
---

[Discussion](https://hashnode.com/posts/kafka-chaos-testing-restart-vs-kill/6afc48e1485f929a3f847aeb)

Comment [Chaos drills for a streaming system: what restarting and killing every component taught me](https://hashnode.com/posts/kafka-chaos-testing-restart-vs-kill/6afc48e1485f929a3f847aeb)

[Mike Dabydeen](https://hashnode.com/@firelinks)

[5h ago](https://hashnode.com/posts/kafka-chaos-testing-restart-vs-kill/6afc48e1485f929a3f847aeb/comment/6afd97034300b22e5f05ab85)

For "recovered" I'd keep your on-time-window rule and change what you report: a spread over repeated kills, because where the kill lands in the commit cycle decides how much the processor replays. Quix Streams commits offsets and state every 5 seconds by default, and a killed processor resumes from the last commit. A kill just after a commit replays almost nothing; one just before it replays close to five seconds of input, which has to drain before the screen is on time again.

So I'd run each kill about 20 times, with a random delay so the signal lands at different points in that cycle, and report the median and the worst run side by side. Your single-sample caveat already names the gap, and I'd expect this to be the variable behind most of it.
