You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jun Rao (Jira)" <ji...@apache.org> on 2024/11/14 15:46:00 UTC

[jira] [Resolved] (KAFKA-17510) Refactor code between SharePartitionManager and DelayedShareFetch for share partition initialization

     [ https://issues.apache.org/jira/browse/KAFKA-17510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jun Rao resolved KAFKA-17510.
-----------------------------
    Fix Version/s: 4.0.0
       Resolution: Fixed

merged the PR to trunk

> 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
>             Fix For: 4.0.0
>
>
> In reference to comment [https://github.com/apache/kafka/pull/16969#discussion_r1750754052] and [https://github.com/apache/kafka/pull/17380#issuecomment-2401324630] , 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)