[ 
https://issues.apache.org/jira/browse/KAFKA-17439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kirk True updated KAFKA-17439:
------------------------------
    Labels: consumer-threading-refactor kip-848-client-support  (was: 
consumer-threading-refactor)

> Make polling for new records an explicit action/event in the new consumer
> -------------------------------------------------------------------------
>
>                 Key: KAFKA-17439
>                 URL: https://issues.apache.org/jira/browse/KAFKA-17439
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients, consumer
>    Affects Versions: 3.7.0
>            Reporter: Kirk True
>            Assignee: Kirk True
>            Priority: Major
>              Labels: consumer-threading-refactor, kip-848-client-support
>             Fix For: 4.0.0
>
>
> Presently, the new consumer polls the FetchRequestManager many, many times a 
> second and creates fetch requests for any fetchable partitions. In order to 
> more closely mirror how the existing consumer processes fetches, we should 
> mirror the points at which fetch requests are sent in the new consumer.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to