[KAFKA-16169] FencedException in commitAsync not propagated without callback

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 3.8.0
• Component/s: clients, consumer
• Labels: kip-848-client-support
• Assignee: Lucas Brutschy
• Reporter: Lucas Brutschy
• Created: 19/Jan/24 14:07
• Updated: 05/Mar/24 08:45
• Resolved: 05/Mar/24 08:45

Description

The javadocs for commitAsync() (w/o callback) say:
@throws org.apache.kafka.common.errors.FencedInstanceIdException if this consumer instance gets fenced by broker.
 
If no callback is passed into commitAsync(), no offset commit callback invocation is submitted. However, we only check for a FencedInstanceIdException when we execute a callback. It seems to me that with commitAsync() we would not throw at all when the consumer gets fenced.
In any case, we need a unit test that verifies that the FencedInstanceIdException is thrown for each version of commitAsync().
 

Issue Links

• links to: GitHub Pull Request #15437