[jira] [Resolved] (KAFKA-19426) TopicBasedRemoteLogMetadataManager's initial should happen after the broker ready

["Chia-Ping Tsai (Jira)" <ji...@apache.org>]

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

Chia-Ping Tsai resolved KAFKA-19426.
------------------------------------
    Fix Version/s: 4.2.0
         Assignee: fujian
       Resolution: Fixed

> TopicBasedRemoteLogMetadataManager's initial should happen after the broker ready
> ---------------------------------------------------------------------------------
>
>                 Key: KAFKA-19426
>                 URL: https://issues.apache.org/jira/browse/KAFKA-19426
>             Project: Kafka
>          Issue Type: Bug
>          Components: Tiered-Storage
>    Affects Versions: 3.8.1, 3.9.0, 4.0.0
>            Reporter: fujian
>            Assignee: fujian
>            Priority: Major
>             Fix For: 4.2.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
>  
> currently. the default value don't make sure the retry can always happen with successful
> For example: There are possible two timeout (2 * 60s) happen at TopicBasedRemoteLogMetadataManager#initializeResources
> [2025-06-03 21:57:21,151] INFO Topic __remote_log_metadata does not exist. Error: Timed out waiting for a node assignment. Call: listNodes at
> [2025-06-03 21:58:21,153] ERROR Encountered error while creating __remote_log_metadata topic. java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.TimeoutException: Timed out waiting for a node assignment. Call: createTopics at
>  
> this original default configure value request the server must be ready within 2 minutes. Not every broker can reach this requirement.
> So propose the [KIP-1197| https://cwiki.apache.org/confluence/display/KAFKA/KIP-1197%3A+Introduce+new+method+to+improve+the+TopicBasedRemoteLogMetadataManager%27s+initialization]
>  



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