[
https://issues.apache.org/jira/browse/KAFKA-18527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914130#comment-17914130
]
TengYao Chi commented on KAFKA-18527:
-------------------------------------
Hi Lianet Magrans,
Some tests in SaslClientsWithInvalidCredentialsTest.scala are failing after
enabling KRaft.
While authentication failures are expected in these tests, consumer#poll
doesn't return until the test timeout occurs.
I found that the consumer keeps attempting to find coordinator even after
authentication failure, which is similar to issue 18157. Is this behavior
expected?
If I understand correctly, an authentication failure should be considered a
fatal error, but it seems the new consumer doesn't have a related mechanism to
handle this scenario.
> SaslClientsWithInvalidCredentialsTest.java and
> SaslClientsWithInvalidCredentialsTest.scala should run for async consumer
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-18527
> URL: https://issues.apache.org/jira/browse/KAFKA-18527
> Project: Kafka
> Issue Type: Sub-task
> Reporter: 黃竣陽
> Assignee: TengYao Chi
> Priority: Blocker
> Labels: kip-848-client-support
> Fix For: 4.0.0
>
>
> All tests in the file are parametrized to run for Classic only, so they won't
> run with the new async consumer. We should enabled them so that they run both
> both consumers.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
