Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
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
Attachments
Issue Links
- links to