[KAFKA-16815] Handle FencedInstanceId on heartbeat for new consumer

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.8.0
• Component/s: clients, consumer
• Labels: kip-848-client-support
• Assignee: Lianet Magrans
• Reporter: Lianet Magrans
• Reviewer: David Jacot
• Created: 22/May/24 13:49
• Updated: 24/May/24 12:20
• Resolved: 24/May/24 12:20

Description

With the new consumer group protocol, a member could receive a FencedInstanceIdError in the heartbeat response. This could be the case when an active member using a group instance id is removed from the group by an admin client. If a second member joins with the same instance id, the first member will receive a FencedInstanceId on the next heartbeat response. This should be treated as a fatal error (consumer should not attempt to rejoin). 

Currently, the FencedInstanceId is not explicitly handled by the client in the HeartbeatRequestManager. It ends up being treated as a fatal error, see here (just because it lands on the "unexpected" error category). We should handle it explicitly, just to make sure that we express that it's is an expected error: log a proper message for it and fail (handleFatalFailure). We should also that the error is included in the tests that cover the HB request error handling (here)

    

Issue Links

• links to: GitHub Pull Request #16047