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

Posted to jira@kafka.apache.org by "Mickael Maison (Jira)" <ji...@apache.org> on 2023/05/05 14:00:00 UTC

[jira] [Commented] (KAFKA-14805) KRaft Controller shouldn't allow metadata updates before migration starts

    [ https://issues.apache.org/jira/browse/KAFKA-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17719878#comment-17719878 ] 

Mickael Maison commented on KAFKA-14805:
----------------------------------------

[~mumrah] The associated PR is merged, is this work complete? Otherwise does this need to be in 3.5?

> KRaft Controller shouldn't allow metadata updates before migration starts
> -------------------------------------------------------------------------
>
>                 Key: KAFKA-14805
>                 URL: https://issues.apache.org/jira/browse/KAFKA-14805
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: kraft
>            Reporter: David Arthur
>            Assignee: David Arthur
>            Priority: Critical
>             Fix For: 3.5.0
>
>
> When starting a ZK to KRaft migration, the new KRaft quorum should not accept external metadata updates from things like CreateTopics or AllocateProducerIds. Having metadata present in the log prior to the migration can lead to undefined state, which is not great.
> This is currently causing test failures on trunk because some producer is allocating a producer ID between the time the KRaft quorum starts and the migration starts.



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