[jira] [Updated] (KAFKA-15261) ReplicaFetcher thread should not block if RLMM is not initialized

["Satish Duggana (Jira)" <ji...@apache.org>]

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

Satish Duggana updated KAFKA-15261:
-----------------------------------
    Priority: Blocker  (was: Major)

> ReplicaFetcher thread should not block if RLMM is not initialized
> -----------------------------------------------------------------
>
>                 Key: KAFKA-15261
>                 URL: https://issues.apache.org/jira/browse/KAFKA-15261
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Abhijeet Kumar
>            Assignee: Abhijeet Kumar
>            Priority: Blocker
>             Fix For: 3.6.0
>
>
> While building remote log aux state, the replica fetcher fetches the remote log segment metadata. If the TBRLMM is not initialized yet, the call blocks. Since replica fetchers share a common lock, it prevents other replica fetchers from running as well. Also the same lock is shared in the handle LeaderAndISR request path, hence those calls get blocked as well.
> Instead, replica fetcher should check if RLMM is initialized before attempting to fetch the remote log segment metadata. If RLMM is not initialized, it should throw a retryable error so that it can be retried later, and also does not block other operations.



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