KIP-1082 — Require Client-Generated IDs over the ConsumerGroupHeartbeat RPC

Accepted Kafka 4.0 ConsumerProtocol

Requires clients to generate and send member IDs on the initial `ConsumerGroupHeartbeat` RPC rather than letting the broker assign them, making the first heartbeat idempotent. Without client-generated IDs, a consumer that sends a join heartbeat but closes before receiving the response may issue a leave heartbeat with a null member ID, causing the broker to register an orphaned member that never expires.

Protocol Impact

ConsumerGroupHeartbeat v1 · Heartbeat

Details