Chirag Wadhwa f9064f8bcd KAFKA-19231-1: Handle fetch request when share session cache is full (#19701) ... According to the recent changes in KIP-932, when the share session cache is full and a broker receives a Share Fetch request with Initial Share Session Epoch (0), then the error code `SHARE_SESSION_LIMIT_REACHED` is returned after a delay of maxWaitMs. This PR implements this logic. In order to add a delay between subsequent share fetch requests, the timer is delayed operation purgatory is used. A new `IdleShareFetchTimeTask` has been added which takes in a CompletableFuture<Void>. Upon the expiration, this future is completed with null. When the future is completes, a response is sent back to the client with the error code `SHARE_SESSION_LIMIT_REACHED` Reviewers: Andrew Schofield <aschofield@confluent.io>, Apoorv Mittal <apoorvmittal10@gmail.com>		2025-05-15 14:36:44 +01:00
..
src	KAFKA-19231-1: Handle fetch request when share session cache is full (#19701)	2025-05-15 14:36:44 +01:00