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년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠