...

To address the issue mentioned in the Motivation section, we propose bumping the version of the ConsumerGroupHeartbeat RPC from version 0 to version 1.

In the current version of the ConsumerGroupHeartbeat RPC, the client can generate and provide a member ID in the heartbeat request. If the client does not provide a member ID, the server will generate one and return it to the client.

In the proposed new version of the ConsumerGroupHeartbeat RPC
In this newer version, the server will require the no longer generate a member ID in all requests. The client will . Instead, the client must generate a UUID as the member ID during the initial heartbeat and continue using it throughout the entire sessioninclude it in every subsequent request. The server will verify validate that a valid UUID is attached provided in the member ID field. EssentiallyIf the member ID is missing, the server will no longer generate the member ID; instead, it must be provided by the client in every reject the request.

Compatibility, Deprecation, and Migration Plan

...