Kirk True created KAFKA-15652:
---------------------------------
Summary: Investigate resetting offsets in
SubscriptionState.resetInitializingPositions()
Key: KAFKA-15652
URL: https://issues.apache.org/jira/browse/KAFKA-15652
Project: Kafka
Issue Type: Sub-task
Components: clients, consumer
Reporter: Kirk True
Assignee: Kirk True
In the {{assign()}} method implementation, both {{KafkaConsumer}} and
{{PrototypeAsyncConsumer}} commit offsets asynchronously. Is this intentional?
[~junrao] asks in a [recent PR
review|https://github.com/apache/kafka/pull/14406/files/193af8230d0c61853d764cbbe29bca2fc6361af9#r1349023459]:
{quote}Do we guarantee that the new owner of the unsubscribed partitions could
pick up the latest committed offset?
{quote}
Let's confirm whether the asynchronous approach is acceptable and correct. If
it is, great, let's enhance the documentation to briefly explain why. If it is
not, let's correct the behavior if it's within the API semantic expectations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
