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

Posted to jira@kafka.apache.org by "Omnia Ibrahim (Jira)" <ji...@apache.org> on 2023/08/02 15:06:00 UTC

[jira] [Commented] (KAFKA-15102) Mirror Maker 2 - KIP690 backward compatibility

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

Omnia Ibrahim commented on KAFKA-15102:
---------------------------------------

The KIP is accepted and the PR is ready

> Mirror Maker 2 - KIP690 backward compatibility
> ----------------------------------------------
>
>                 Key: KAFKA-15102
>                 URL: https://issues.apache.org/jira/browse/KAFKA-15102
>             Project: Kafka
>          Issue Type: Bug
>          Components: mirrormaker
>    Affects Versions: 3.1.0
>            Reporter: David Dufour
>            Assignee: Omnia Ibrahim
>            Priority: Major
>             Fix For: 3.3, 3.2.4, 3.1.3, 3.6.0, 3.4.2, 3.5.2
>
>
> According to KIP690, "When users upgrade an existing MM2 cluster they don’t need to change any of their current configuration as this proposal maintains the default behaviour for MM2."
> Now, the separator is subject to customization.
> As a consequence, when an MM2 upgrade is performed, if the separator was customized with replication.policy.separator, the name of this internal topic changes. It then generates issues like:
> Caused by: java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.InvalidTopicException: Topic 'mm2-offset-syncs_bkts28_internal' collides with existing topics: mm2-offset-syncs.bkts28.internal
> It has been observed that the replication can then be broken sometimes several days after the upgrade (reason not identified). By deleting the old topic name, it recovers.



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