...

In the new version of the ConsumerGroupHeartbeat RPC , the client must generate a UUID as the member ID during the initial heartbeat. This UUID member ID must be included in every subsequent request to ensure consistency. The server will validate that a valid UUID is provided in the member ID field. If the member ID is missing or invalid, the server will reject the request with an InvalidRequestException .

Last, to accommodate these updates, we also propose bumping the ConsumerGroupHeartbeat RPC from version 0 to version 1. This version upgrade reflects the new requirement for client-generated member IDs. It's important to note that despite these behavioral changes, there are no modifications to the existing fields themselves.

Proposed Changes

To implement the changes proposed in the KIP, the client will need to generate UUIDs. The simple specifications are as follows:

...

The change is backward compatible because version 0 of the ConsumerGroupHeartbeat RPC already supports a member ID provided by the client. If a client using an older version sends a heartbeat, it will still follow the rules outlined in KIP-848#Member ID. Newer clients should generate the member ID on the client side because this approach reduces dependency on the server for ID management, minimizes the risk of ID conflicts, and enhances scalability by distributing the responsibility of unique ID generation. 

...