[
https://issues.apache.org/jira/browse/KAFKA-17742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-17742.
-----------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
merged the PR to trunk.
> Move DelayedShareFetchPurgatory declaration to ReplicaManager
> -------------------------------------------------------------
>
> Key: KAFKA-17742
> URL: https://issues.apache.org/jira/browse/KAFKA-17742
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Abhinav Dixit
> Assignee: Abhinav Dixit
> Priority: Major
> Fix For: 4.0.0
>
>
> Hi, as per comments
> [https://github.com/apache/kafka/pull/17380#issuecomment-2399040546] and
> [https://github.com/apache/kafka/pull/17380#issuecomment-2400431605] , we
> need to do the following -
> # Declare the delayed share fetch purgatory inside ReplicaManager along with
> the existing purgatories. We don't need a reference to this purgatory outside
> of ReplicaManager, we can just add accessor methods.
> # Currently, we check the produce/fetch purgatory when a replica becomes the
> follower or a replica is deleted from a broker through ReplicaManager.
> applyLocalFollowersDelta and ReplicaManager.applyDelta. We should do the same
> for share purgatory.
> # Perform a {{checkAndComplete}} when HWM is updated
> # Perform a shutdown of the delayed share fetch purgatory like the others in
> ReplicaManager
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
