[
https://issues.apache.org/jira/browse/KAFKA-18166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divij Vaidya updated KAFKA-18166:
---------------------------------
Affects Version/s: 3.9.0
> Indefinite timeout when publishing events to RLMM (RemoteLogMetadataManager)
> ----------------------------------------------------------------------------
>
> Key: KAFKA-18166
> URL: https://issues.apache.org/jira/browse/KAFKA-18166
> Project: Kafka
> Issue Type: Improvement
> Components: Tiered-Storage
> Affects Versions: 4.0.0, 3.9.0
> Reporter: Divij Vaidya
> Priority: Minor
> Labels: newbie
>
> RemoteLogManager has multiple instances where we are doing a
> {{CompletableFuture.get()}} without setting its timeout parameter. Ideally,
> we do not want indefinite wait in the code base which depends on external
> components such as RemoteLogMetadataManager. For example, the code would
> "hang" if the underlying RLMM is not available or very slow for some reason.
> The objective of this task is to set a reasonable timeout (my suggestion is 1
> sec) on these futures. You will also need to handle the ensuing
> TimeoutException accordingly.
> [https://github.com/apache/kafka/blob/50b6953661a46d7d57a8aca5c875e91a19166253/core/src/main/java/kafka/log/remote/RemoteLogManager.java#L572]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
