[
https://issues.apache.org/jira/browse/KAFKA-15553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk True updated KAFKA-15553:
------------------------------
Component/s: clients
> Review committed offset refresh logic
> -------------------------------------
>
> Key: KAFKA-15553
> URL: https://issues.apache.org/jira/browse/KAFKA-15553
> Project: Kafka
> Issue Type: Sub-task
> Components: clients, consumer
> Reporter: Philip Nee
> Assignee: Philip Nee
> Priority: Major
> Labels: consumer-threading-refactor
>
> From the exsiting 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
