Automatically update brokerstring in MSK

0

A customer is looking to migrate their kafka workload to MSK. they have a question on how to mange the broker strings when a scaling event occurs in the cluster. for example: the producer has a config which has a property:
bootstrap.servers={comma separated string of 3 broker urls}

now a scaling event occurs and now you have another broker. Now the ugly way is to update the brokerstring url section manually.

the other option is to use a round robin DNS or an ALB and all the clients(producers/consumers) talk to the endpoint and behind the scenes it maintains the broker strings.

though i doubt if second option is doable since MSK is managed. or may be i am understanding it incorrectly?

Looking for some guidance on how this scenario is solved for other customers.

AWS
專家
已提問 4 年前檢視次數 812 次
1 個回答
1
已接受的答案

Is there a specific reason why they want to add newly added broker into the brokerstring?

The use of bootstrap.servers by producer/consumer is to get the metadata of the Kafka cluster i.e. list of brokers, partition/offset information to discover the Kafka cluster. Any broker can be bootstrap server because every broker receives metadata information.

To summarize, it is not necessary to update bootstrap servers every time a new broker is added. The producers/consumers can still operate with existing brokerstring of limited brokers

AWS
已回答 4 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南