[
https://issues.apache.org/jira/browse/KAFKA-16169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17808701#comment-17808701
]
Lianet Magrans commented on KAFKA-16169:
----------------------------------------
Hey [~lbrutschy], I'm currently working on some fixes for the error handling in
commit (sync and async) so I could take this one if that's ok.
> 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
> Priority: Major
>
> 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)
