• config.properties.exclude

    Topic config properties that should not be replicated. Supports comma-separated property names and regexes.

    Type:list
    Default:follower.replication.throttled.replicas,leader.replication.throttled.replicas,message.timestamp.difference.max.ms,log.message.timestamp.before.max.ms,log.message.timestamp.after.max.ms,message.timestamp.type,unclean.leader.election.enable,min.insync.replicas
    Valid Values:
    Importance:high

  • topics

    Topics to replicate. Supports comma-separated topic names and regexes.

    Type:list
    Default:.*
    Valid Values:
    Importance:high

  • topics.exclude

    Excluded topics. Supports comma-separated topic names and regexes. Excludes take precedence over includes.

    Type:list
    Default:mm2.*\.internal,.*\.replica,__.*
    Valid Values:
    Importance:high

  • config.property.filter.class

    ConfigPropertyFilter to use. Selects topic config properties to replicate.

    Type:class
    Default:org.apache.kafka.connect.mirror.DefaultConfigPropertyFilter
    Valid Values:
    Importance:low

  • consumer.poll.timeout.ms

    Timeout when polling source cluster.

    Type:long
    Default:1000 (1 second)
    Valid Values:
    Importance:low

  • emit.offset-syncs.enabled

    Whether to store the new offset of the replicated records in offset-syncs topic or not. MirrorCheckpointConnector will not be able to sync group offsets or emit checkpoints if emit.checkpoints.enabled and/or sync.group.offsets.enabled are enabled while emit.offset-syncs.enabled is disabled.

    Type:boolean
    Default:true
    Valid Values:
    Importance:low

  • heartbeats.replication.enabled

    Whether to replicate the heartbeats topics even when the topic filter does not include them. If set to true, heartbeats topics identified by the replication policy will always be replicated, regardless of the topic filter configuration. If set to false, heartbeats topics will only be replicated if the topic filter allows.

    Type:boolean
    Default:true
    Valid Values:
    Importance:low

  • metric.names.formats

    Deprecated. The formats in which metrics are emitted. Valid values are legacy and new. When set to legacy, the metrics have the following name "kafka.connect.mirror:type=MirrorSourceConnector,source={SOURCE},target={TARGET},topic={TOPIC},partition={PARTITION}". When set to new, the metrics have the following name "kafka.connect:type=plugins,connector={CONNECTOR},task={TASK},source={SOURCE},target={TARGET},topic={TOPIC},partition={PARTITION}". When set to "legacy,new" the connector will emit metrics with both names, this can be useful when migrating to the new format but it doubles the amount of metrics that are emitted.
    In Kafka 5.0 the legacy format and this configuration will be removed and the metrics will always use the new names.

    Type:list
    Default:legacy
    Valid Values:[legacy, new]
    Importance:low

  • offset-syncs.topic.location

    The location (source/target) of the offset-syncs topic.

    Type:string
    Default:source
    Valid Values:[source, target]
    Importance:low

  • offset-syncs.topic.replication.factor

    Replication factor for offset-syncs topic.

    Type:short
    Default:3
    Valid Values:
    Importance:low

  • offset.lag.max

    Defines the maximum lag (downstream offset - last synced downstream offset) threshold before MirrorSourceTask generates an offset-sync (upstream-downstream offset mapping) record during partition replication. In practice: Setting this value to 100 will produce an offset-sync at least after every 100 records. Lowering this value increases the precision of the consumer offset checkpoints created by the MirrorCheckpointTask based on the offset-syncs. This is particularly beneficial for low-lag consumers reading from the end of a topic. Conversely, when a consumer operates with high lag, checkpoint precision may degrade due to internal optimizations. Setting this value to 0 forces an offset-sync for every replicated record. While this maximizes precision, it may incur performance and storage overhead for high-throughput topics. A higher value can reduce the footprint of the offset-sync topic, but may result in excessive record duplication (consumer reprocessing) during a failover. Partition Count * offset.lag.max = Approximate duplicated record count (Actual value can be lower or even higher depending on timing and consumer lag)

    Type:long
    Default:100
    Valid Values:
    Importance:low

  • refresh.topics.enabled

    Whether to periodically check for new topics and partitions.

    Type:boolean
    Default:true
    Valid Values:
    Importance:low

  • refresh.topics.interval.seconds

    Frequency of topic refresh.

    Type:long
    Default:600
    Valid Values:
    Importance:low

  • replication.factor

    Replication factor for newly created remote topics.

    Type:int
    Default:2
    Valid Values:
    Importance:low

  • sync.topic.acls.enabled

    Whether to periodically configure remote topic ACLs to match their corresponding upstream topics.

    Type:boolean
    Default:true
    Valid Values:
    Importance:low

  • sync.topic.acls.interval.seconds

    Frequency of topic ACL sync.

    Type:long
    Default:600
    Valid Values:
    Importance:low

  • sync.topic.configs.enabled

    Whether to periodically configure remote topics to match their corresponding upstream topics.

    Type:boolean
    Default:true
    Valid Values:
    Importance:low

  • sync.topic.configs.interval.seconds

    Frequency of topic config sync.

    Type:long
    Default:600
    Valid Values:
    Importance:low

  • topic.filter.class

    TopicFilter to use. Selects topics to replicate.

    Type:class
    Default:org.apache.kafka.connect.mirror.DefaultTopicFilter
    Valid Values:
    Importance:low