[
https://issues.apache.org/jira/browse/KAFKA-17510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinav Dixit updated KAFKA-17510:
----------------------------------
Description:
In reference to comment
[https://github.com/apache/kafka/pull/16969#discussion_r1750754052] , we need
to refactor code between SharePartitionManager and DelayedShareFetch so that
the initialization error of share partition gets considered.
Also, If a sharePartition is being initialized, any pending shareFetchRequest
is blocked in the purgatory. So, after the initialization completes, we need to
trigger a check in the share fetch purgatory to wake up pending delayed
operations.
was:In reference to comment
[https://github.com/apache/kafka/pull/16969#discussion_r1750754052] , we need
to refactor code between SharePartitionManager and DelayedShareFetch so that
the initialization error of share partition gets considered.
> Refactor code between SharePartitionManager and DelayedShareFetch for share
> partition initialization
> ----------------------------------------------------------------------------------------------------
>
> Key: KAFKA-17510
> URL: https://issues.apache.org/jira/browse/KAFKA-17510
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Abhinav Dixit
> Assignee: Apoorv Mittal
> Priority: Major
>
> In reference to comment
> [https://github.com/apache/kafka/pull/16969#discussion_r1750754052] , we need
> to refactor code between SharePartitionManager and DelayedShareFetch so that
> the initialization error of share partition gets considered.
> Also, If a sharePartition is being initialized, any pending shareFetchRequest
> is blocked in the purgatory. So, after the initialization completes, we need
> to trigger a check in the share fetch purgatory to wake up pending delayed
> operations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
