[ https://issues.apache.org/jira/browse/KAFKA-16169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lucas Brutschy reassigned KAFKA-16169: -------------------------------------- Assignee: Lucas Brutschy (was: Lianet Magrans) > FencedException in commitAsync not propagated without callback > -------------------------------------------------------------- > > Key: KAFKA-16169 > URL: https://issues.apache.org/jira/browse/KAFKA-16169 > Project: Kafka > Issue Type: Bug > Components: clients, consumer > Reporter: Lucas Brutschy > Assignee: Lucas Brutschy > Priority: Critical > Labels: kip-848-client-support > Fix For: 3.8.0 > > > 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(){}}}. > -- This message was sent by Atlassian Jira (v8.20.10#820010)