[ https://issues.apache.org/jira/browse/KAFKA-17209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kirk True updated KAFKA-17209: ------------------------------ Labels: kip-848-client-support (was: ) > Revisit testCurrentLag for AsyncKafkaConsumer > --------------------------------------------- > > Key: KAFKA-17209 > URL: https://issues.apache.org/jira/browse/KAFKA-17209 > Project: Kafka > Issue Type: Test > Components: clients, unit tests > Reporter: TaiJuWu > Assignee: TaiJuWu > Priority: Major > Labels: kip-848-client-support > > The difference between {{ClassicConsumer}} and {{AsyncConsumer}} is > ClassicConsumer is single thread and AsyncConsumer is two thread, one is app > thread, the other is background thread. > {{Fetch}} Request is generated by background thread and {{ListOffset}} > Request is generated by application thread. > This will make {{testCurrentLag}} fail if AsyncConsumer generated {{Fetch > Request}} first. > So we support out of order feature for {{MockClient}} to resolve issue. > Another difference between asyncConsumer and ClassicConsumer is front do > generate additional {{FetchOffset}} Request from CommitRequestManager but > ClassicConsumer does not have the request. > The reason is coordinator is not ready during test for {{ClassicConsumer}} so > we can ignore this request for {{AsyncConsumer.}} -- This message was sent by Atlassian Jira (v8.20.10#820010)