You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Apoorv Mittal (Jira)" <ji...@apache.org> on 2026/04/09 09:11:00 UTC

[jira] [Resolved] (KAFKA-20425) Avoid triggers to purgatory when no data is available for share fetch

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

Apoorv Mittal resolved KAFKA-20425.
-----------------------------------
    Resolution: Fixed

> Avoid triggers to purgatory when no data is available for share fetch
> ---------------------------------------------------------------------
>
>                 Key: KAFKA-20425
>                 URL: https://issues.apache.org/jira/browse/KAFKA-20425
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Apoorv Mittal
>            Assignee: Apoorv Mittal
>            Priority: Major
>
> The delayed share fetch triggers waiting requests for same topic partition in purgatory for which the request has been completed. This is needed as for same sahre partition there can be requests in purgatory waiting to acquire lock. However, the triggers are always not needed i.e. when no data is available in partition hence these triggers can be avoided.



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