[jira] [Updated] (KAFKA-13376) Allow MirrorMaker 2 producer and consumer customization per replication flow

2021-10-14 Thread Ivan Yurchenko (Jira)


 [ 
https://issues.apache.org/jira/browse/KAFKA-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Yurchenko updated KAFKA-13376:
---
Description: 
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}


  was:
Currently, it's possible to set producer and consumer configurations for a 
cluster in MirrorMaker, 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}



> 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)


[jira] [Updated] (KAFKA-13376) Allow MirrorMaker 2 producer and consumer customization per replication flow

2021-10-14 Thread Ivan Yurchenko (Jira)


 [ 
https://issues.apache.org/jira/browse/KAFKA-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Yurchenko updated KAFKA-13376:
---
Summary: Allow MirrorMaker 2 producer and consumer customization per 
replication flow  (was: Allow MirrorMaker producer and consumer customization 
per replication flow)

> 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, 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)