[
https://issues.apache.org/jira/browse/KAFKA-12743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17338607#comment-17338607
]
Guozhang Wang commented on KAFKA-12743:
---------------------------------------
Yeah that's a good point.
I think your workaround makes sense -- since you could just have a separate
application for manual failover anyways, it should be fine then.
Moving forward, we should have a better way of DR story for Kafka Streams,
maybe allowing users to totally customize their changelog topics. For that
reason, please keep this ticket open so that we can revisit.
> [Kafka Streams] - regex name for state-store change-log topic
> -------------------------------------------------------------
>
> Key: KAFKA-12743
> URL: https://issues.apache.org/jira/browse/KAFKA-12743
> Project: Kafka
> Issue Type: Improvement
> Components: mirrormaker, streams
> Affects Versions: 2.8.0
> Reporter: Sergey Zyrianov
> Priority: Major
>
> Currently, when working with Kafka backed state stores in Kafka Streams,
> these log compacted topics are given a hardcoded name :
> _app_id-storename-changelog_
> {noformat}
> public static String storeChangelogTopic(String applicationId, String
> storeName) {
> return applicationId + "-" + storeName + STATE_CHANGELOG_TOPIC_SUFFIX;
> }{noformat}
>
> MirrorMaker2(mm2) copies these topics to remote cluster under the name
> _src-cluster-alias.app_id-storename-changelog_
>
> When streams app fails over to the remote cluster it has troubles to find
> changelog topic of its state store since it was renamed - given source
> cluster prefix by mm2.
> Whats the fix should be ? instruct mm2 to keep topic name or subscribe to
> regex *._app_id-storename-changelog_ topic name for the state's changelog.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
