[
https://issues.apache.org/jira/browse/KAFKA-17395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17876164#comment-17876164
]
TaiJuWu edited comment on KAFKA-17395 at 8/23/24 8:49 AM:
----------------------------------------------------------
Hi [~lianetm] ,
In my mind, there is a scenario make this test fail.
The response is prepare by app thread and the response retrived by background
thread.
In current MockClient implement, we can't make sure response always parepare
before background thread every time. This is root cause of failure.
If the response is put after background thread try to retrive, we can't get the
response.
I think MockClient needs to enhance some synchronous feature to support both
classic and asynchronous consumer.
Is it reasonable or something I missed, thanks.
was (Author: JIRAUSER301374):
Hi [~lianetm] ,
In my mind, there is a scenario make this test fail.
The response is prepare by app thread and the response retrived by background
thread.
In current MockClient implement, we can't make sure response always parepare
before background thread every time.
If the response is put after background thread try to retrive, we can't get the
response.
Is it reasonable? Or something I missed, thanks.
> Flaky test testMissingOffsetNoResetPolicy for new consumer
> ----------------------------------------------------------
>
> Key: KAFKA-17395
> URL: https://issues.apache.org/jira/browse/KAFKA-17395
> Project: Kafka
> Issue Type: Bug
> Components: clients, consumer
> Reporter: Lianet Magrans
> Priority: Major
> Labels: consumer-threading-refactor, flaky-test
>
> KafkaConsumerTest.testMissingOffsetNoResetPolicy is flaky when running for
> the new consumer (passing consistently for the classic consumer).
> Fails with :
> org.opentest4j.AssertionFailedError: Condition not met within timeout 15000.
> Consumer was not able to update fetch positions on continuous calls with 0
> timeout ==> expected: <true> but was: <false>
> It's been flaky since it was enabled for the new consumer with
> [https://github.com/apache/kafka/pull/16587]
> See last couple of month runs on trunk showing the flakiness:
> [https://ge.apache.org/scans/tests?search.names=Git%20branch&search.rootProjectNames=kafka&search.startTimeMax=1724299199999&search.startTimeMin=1717214400000&search.timeZoneId=America%2FToronto&search.values=trunk&tests.container=org.apache.kafka.clients.consumer.KafkaConsumerTest&tests.test=testMissingOffsetNoResetPolicy(GroupProtocol)%5B2%5D]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
