[PR] KAFKA-20425: Avoid triggers to purgatory when no data is available for share fetch [kafka]

["apoorvmittal10 (via GitHub)" <gi...@apache.org>]

apoorvmittal10 opened a new pull request, #22005:
URL: https://github.com/apache/kafka/pull/22005

   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 is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: jira-unsubscribe@kafka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] KAFKA-20425: Optimize purgatory triggers when no data is available for share fetch [kafka]

["apoorvmittal10 (via GitHub)" <gi...@apache.org>]

apoorvmittal10 merged PR #22005:
URL: https://github.com/apache/kafka/pull/22005


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: jira-unsubscribe@kafka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org