[
https://issues.apache.org/jira/browse/KAFKA-15553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877813#comment-17877813
]
Colin McCabe commented on KAFKA-15553:
--------------------------------------
Changing target fix version to 4.0 since this is not a blocker and we are past
code freeze
> Review consumer positions update
> --------------------------------
>
> Key: KAFKA-15553
> URL: https://issues.apache.org/jira/browse/KAFKA-15553
> Project: Kafka
> Issue Type: Task
> Components: clients, consumer
> Reporter: Philip Nee
> Assignee: Philip Nee
> Priority: Minor
> Labels: consumer-threading-refactor, position
> Fix For: 3.9.0
>
>
> From the existing comment: If there are any partitions which do not have a
> valid position and are not awaiting reset, then we need to fetch committed
> offsets.
> In the async consumer: I wonder if it would make sense to refresh the
> position on the event loop continuously.
> The logic to refresh offsets in the poll loop is quite fragile and works
> largely by side-effects of the code that it calls. For example, the behaviour
> of the "cached" value is really not that straightforward and simply reading
> the cached value is not sufficient to start consuming data in all cases.
> This area needs a bit of a refactor.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
