[jira] [Created] (KAFKA-15558) Determine if Timer should be used elsewhere in PrototypeAsyncConsumer.updateFetchPositions()

["Kirk True (Jira)" <ji...@apache.org>]

Kirk True created KAFKA-15558:
---------------------------------

             Summary: Determine if Timer should be used elsewhere in PrototypeAsyncConsumer.updateFetchPositions()
                 Key: KAFKA-15558
                 URL: https://issues.apache.org/jira/browse/KAFKA-15558
             Project: Kafka
          Issue Type: Sub-task
            Reporter: Kirk True


This is a followup ticket based on a question from [~junrao] when reviewing the [fetch request manager pull request|https://github.com/apache/kafka/pull/14406]:
{quote}It still seems weird that we only use the timer for {{{}refreshCommittedOffsetsIfNeeded{}}}, but not for other cases where we don't have valid fetch positions. For example, if all partitions are in {{AWAIT_VALIDATION}} state, it seems that {{PrototypeAsyncConsumer.poll()}} will just go in a busy loop, which is not efficient.
{quote}
The goal here is to determine if we should also be propagating the Timer to the validate positions and reset positions operations.



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