[jira] [Resolved] (KAFKA-10332) MirrorMaker2 fails to detect topic if remote topic is created first

["Randall Hauch (Jira)" <ji...@apache.org>]

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

Randall Hauch resolved KAFKA-10332.
-----------------------------------
    Fix Version/s: 2.6.1
                   2.5.2
                   2.7.0
         Reviewer: Randall Hauch
       Resolution: Fixed

Merged to the `trunk` branch (for future 2.8 release), and cherry-picked to the `2.7` for inclusion in the upcoming 2.7.0, the `2.6` branch for inclusion in the next 2.6.1 if/when it's released, and the `2.5` branch for the next 2.5.2 if/when it's released.

> MirrorMaker2 fails to detect topic if remote topic is created first
> -------------------------------------------------------------------
>
>                 Key: KAFKA-10332
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10332
>             Project: Kafka
>          Issue Type: Bug
>          Components: mirrormaker
>    Affects Versions: 2.6.0
>            Reporter: Mickael Maison
>            Assignee: Mickael Maison
>            Priority: Major
>             Fix For: 2.7.0, 2.5.2, 2.6.1
>
>
> Setup:
> - 2 clusters: source and target
> - Mirroring data from source to target
> - create a topic called source.mytopic on the target cluster
> - create a topic called mytopic on the source cluster
> At this point, MM2 does not start mirroring the topic.
> This also happens if you delete and recreate a topic that is being mirrored.
> The issue is in [refreshTopicPartitions()|https://github.com/apache/kafka/blob/trunk/connect/mirror/src/main/java/org/apache/kafka/connect/mirror/MirrorSourceConnector.java#L211-L232] which basically does a diff between the 2 clusters.
> When creating the topic on the source cluster last, it makes the partition list of both clusters match, hence not triggering a reconfiguration



--
This message was sent by Atlassian Jira
(v8.3.4#803005)