From the In-flight: the money moving through your Kafka architecture map

Every redrive goes through one method with a dry run and a rate cap

strength · low · verified

Console, MCP and CLI all call Setup.redrive, which refuses queues the catalog does not list (Setup.java:324), allows one run per queue within one process (Setup.java:346) and defaults to a dry run (Mcp.java:528, Api.java:145; the CLI needs --run). Redrive caps the rate at 5000 a second, default 50 (Redrive.java:69), stops at the end offsets seen at start, and marks replays with a redriveof header (Redrive.java:212).

Impact: A single place to add a human approval or a per-agent write capability, inherited by every surface at once.

The console adds a confirm step naming the bootstrap servers (ui/src/panels/Redrive.tsx) and the MCP tool is annotated destructive (Mcp.java:167-169), so clients that honour annotations prompt too. The missing piece is a server-side check that the person, not the caller, chose to write. Replays are not deduplicated: a failed send or a parallel CLI run can write up to 99 records again (Redrive.java:215-227).

The trail

  1. Redrive
  2. MCP Server
  3. Setup Actions and Causes
  4. CLI Setup and Rehearse
Open on the map

More from this board