You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/01/07 17:01:00 UTC

[jira] [Commented] (KAFKA-9337) Simplifying standalone mm2-connect config

    [ https://issues.apache.org/jira/browse/KAFKA-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17009903#comment-17009903 ] 

ASF GitHub Bot commented on KAFKA-9337:
---------------------------------------

mimaison commented on pull request #7872: KAFKA-9337 simplify mm2 initial configs
URL: https://github.com/apache/kafka/pull/7872
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Simplifying standalone mm2-connect config
> -----------------------------------------
>
>                 Key: KAFKA-9337
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9337
>             Project: Kafka
>          Issue Type: Improvement
>          Components: KafkaConnect, mirrormaker
>    Affects Versions: 2.4.0
>            Reporter: karan kumar
>            Priority: Minor
>
> One of the nice things about kafka is setting up in the local environment is really simple. I was giving a try to the latest feature ie MM2 and found it took me some time to get a minimal setup running. 
> Default config provided assumes that there will already be 3 brokers running due to the default replication factor of the admin topics the mm2 connector creates. 
> This got me thinking that most of the people would follow the same approach I followed. 
> 1. Start a single broker cluster on 9092 
> 2. Start another single cluster broker on, let's say, 10002 
> 3. Start mm2 by"./bin/connect-mirror-maker.sh ./config/connect-mirror-maker.properties" 
> What happened was I had to supply a lot more configs 
> This jira is created post discussion on the mailing list:
> https://lists.apache.org/thread.html/%3CCAJXUdH13Kw3nAm3hO69WROzSyoVwUE1nXf9hKcbawC9R-3dnhA@mail.gmail.com%3E
> cc [~ryannedolan]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)