[jira] [Resolved] (KAFKA-14656) Brokers rejecting LISR during ZK migration

["David Arthur (Jira)" <ji...@apache.org>]

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

David Arthur resolved KAFKA-14656.
----------------------------------
    Resolution: Fixed

> Brokers rejecting LISR during ZK migration
> ------------------------------------------
>
>                 Key: KAFKA-14656
>                 URL: https://issues.apache.org/jira/browse/KAFKA-14656
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 3.4.0
>            Reporter: David Arthur
>            Assignee: David Arthur
>            Priority: Blocker
>             Fix For: 3.4.0
>
>
> During the ZK migration, the KRaft controller sends controller RPCs to the ZK brokers (LISR, UMR, etc). Since the migration can begin immediately after a ZK broker starts up with migration enabled, it is possible that this broker is not seen as alive by the rest of the brokers. This is due to the KRaft controller taking over before the ZK controller can send out UMR with the restarted broker.
>  
> The result is that the parts of the LISR sent by KRaft immediately after the metadata migration is rejected by brokers due the leader being offline. 
>  
> The fix for this is to send an UMR to all brokers after the migration with the set of alive brokers.



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