[ https://issues.apache.org/jira/browse/KAFKA-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17432946#comment-17432946 ]
Dongjin Lee commented on KAFKA-13376: ------------------------------------- Hi [~ivanyu], As of present, the replication-level client configuration is not working correctly (although the MirrorMakerConfig's Javadoc states that it works); and [this KIP|https://cwiki.apache.org/confluence/display/KAFKA/KIP-781%3A+Improve+MirrorMaker2%27s+client+configuration] (KAFKA-13365) states the rule for replication-level client configuration like the following: {quote}{{A->B.producer.\{property-name}}} and {{A->B.admin.\{property-name}}} are applied to target cluster clients and {{A->B.consumer.\{property-name}}} is applied to source cluster clients. {quote} If not, please leave a message on the mailing list [here|https://lists.apache.org/thread.html/r2ab9df6e620eb3ac8a0e1dd7a2f833b1978452aa6bec21c38c1dde18%40%3Cdev.kafka.apache.org%3E]. > Allow MirrorMaker 2 producer and consumer customization per replication flow > ---------------------------------------------------------------------------- > > Key: KAFKA-13376 > URL: https://issues.apache.org/jira/browse/KAFKA-13376 > Project: Kafka > Issue Type: Bug > Components: mirrormaker > Reporter: Ivan Yurchenko > Priority: Minor > > Currently, it's possible to set producer and consumer configurations for a > cluster in MirrorMaker 2, like this: > {noformat} > {source}.consumer.{consumer_config_name} > {target}.producer.{producer_config_name} > {noformat} > However, in some cases it makes sense to set these configs differently for > different replication flows (e.g. when they have different latency/throughput > trade-offs), something like: > {noformat} > {source}->{target}.{source}.consumer.{consumer_config_name} > {source}->{target}.{target}.producer.{producer_config_name} > {noformat} -- This message was sent by Atlassian Jira (v8.3.4#803005)