KIP-1371 — Formalize Consumer Reactor Cross-Manager Coordination and Publication

Discussion ConsumerClient

Renames the async consumer's `ConsumerNetworkThread` loop to `ConsumerReactor` and formalizes four concurrency semantics: single-writer manager state, an immutable published view for the application thread, typed next-poll conditions, and publication before effect. The background loop currently compresses every readiness condition (time, coordinator availability, assignment, metadata, buffer capacity, in-flight requests) into a single deadline that cannot distinguish work available now from work waiting on an external input, and different parts of one decision can be published out of order.

Protocol Impact

Fetch · Heartbeat

Details