You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Matthew de Detrich (Jira)" <ji...@apache.org> on 2023/09/11 07:51:00 UTC

[jira] [Resolved] (KAFKA-14975) Make TopicBasedRemoteLogMetadataManager methods wait for initialize to complete

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

Matthew de Detrich resolved KAFKA-14975.
----------------------------------------
    Resolution: Won't Fix

Closing issue since the core problem was solved in another way (see https://github.com/apache/kafka/pull/14127)

> Make TopicBasedRemoteLogMetadataManager methods wait for initialize to complete
> -------------------------------------------------------------------------------
>
>                 Key: KAFKA-14975
>                 URL: https://issues.apache.org/jira/browse/KAFKA-14975
>             Project: Kafka
>          Issue Type: Task
>            Reporter: Matthew de Detrich
>            Assignee: Matthew de Detrich
>            Priority: Major
>
> In the current implementation of TopicBasedRemoteLogMetadataManager various methods internally call the 
> ensureInitializedAndNotClosed to ensure that the TopicBasedRemoteLogMetadataManager is initialized. If TopicBasedRemoteLogMetadataManager is not initialized then an exception will be thrown.
> This is not an ideal behaviour, rather than just throwing an exception we should instead try to wait until TopicBasedRemoteLogMetadataManager is initialised (with a timeout). This is what the expected behaviour from users should be and its also what other parts of Kafka that use plugin based systems (ergo kafka connect) do.



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