9.4 Kafka Client Side Adoption
This topic provides the systematic instructions for Kafka cluster setup.
Changes are required at the client service level which is connected to kafka. User
needs to add the below mentioned properties to those managed servers where:
- plato-alert-management-services
- plato-orch-services
- plato-api-gateway
- conductor
- plato-batch-server
For Spring producer client services below properties are needed:
- -Dspring.cloud.stream.kafka.default.producer.sync=true
Note:
This property is not required on managed server where api-gateway is deployed. - -Dspring.cloud.stream.kafka.default.producer.configuration.max.block.ms=5000
- -Dspring.cloud.stream.kafka.binder.replication-factor=3
- -Dspring.cloud.stream.kafka.binder.required-acks=all
The below properties would already be there in application.yml or property
table, their values would need to be updated as mentioned below for both producer and
consumer services:
- spring.cloud.stream.kafka.binder.brokers: <all brokers separated by comma> e.g. localhost:9092,localhost:9093,localhost:9094
- spring.cloud.stream.kafka.binder.zkNodes: <all zookeepers separated by comma> e.g. localhost:2181,localhost:2182,localhost:2183