[
https://issues.apache.org/jira/browse/KAFKA-10586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Urban updated KAFKA-10586:
---------------------------------
Description:
KIP-382 introduced MirrorMaker 2.0. Because of scoping issues, the dedicated
MirrorMaker 2.0 cluster does not utilize the Connect REST API. This means that
with specific workloads, the dedicated MM2 cluster can become unable to react
to dynamic topic and group filter changes.
(This occurs when after a rebalance operation, the leader node has no
MirrorSourceConnectorTasks. Because of this, the MirrorSourceConnector is
stopped on the leader, meaning it cannot detect config changes by itself.
Followers still running the connector can detect config changes, but they
cannot query the leader for config updates.)
Besides the REST support, config provider references should be evaluated lazily
in connector configurations.
was:
KIP-382 introduced MirrorMaker 2.0. Because of scoping issues, the dedicated
MirrorMaker 2.0 cluster does not utilize the Connect REST API. This means that
with specific workloads, the dedicated MM2 cluster can become unable to react
to dynamic topic and group filter changes.
(This occurs when after a rebalance operation, the leader node has no
MirrorSourceConnectorTasks. Because of this, the MirrorSourceConnector is
stopped on the leader, meaning it cannot detect config changes by itself.
Followers still running the connector can detect config changes, but they
cannot query the leader for config updates.)
> Full support for distributed mode in dedicated MirrorMaker 2.0 clusters
> -----------------------------------------------------------------------
>
> Key: KAFKA-10586
> URL: https://issues.apache.org/jira/browse/KAFKA-10586
> Project: Kafka
> Issue Type: Improvement
> Components: mirrormaker
> Reporter: Daniel Urban
> Assignee: Daniel Urban
> Priority: Major
>
> KIP-382 introduced MirrorMaker 2.0. Because of scoping issues, the dedicated
> MirrorMaker 2.0 cluster does not utilize the Connect REST API. This means
> that with specific workloads, the dedicated MM2 cluster can become unable to
> react to dynamic topic and group filter changes.
> (This occurs when after a rebalance operation, the leader node has no
> MirrorSourceConnectorTasks. Because of this, the MirrorSourceConnector is
> stopped on the leader, meaning it cannot detect config changes by itself.
> Followers still running the connector can detect config changes, but they
> cannot query the leader for config updates.)
> Besides the REST support, config provider references should be evaluated
> lazily in connector configurations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
