Yes, it is possible to have a separate Kraft controller from the brokers in Apache Kafka. The Kraft controller is responsible for managing the overall state of the Kafka cluster, such as managing topics, partitions, and replica assignments.
To set up a separate Kraft controller, you will need to configure the Kafka brokers to point to the new controller using the controller.quorum.voters property in the broker configuration file. This property should be set to a comma-separated list of hostname:port pairs that correspond to the Kraft controller instances. Additionally, you will need to configure the Kraft controller instances to communicate with each other using the controller.quorum.type property in the controller configuration file. This property should be set to static if you are using a fixed set of controllers, or zookeeper if you are using ZooKeeper for controller discovery. There is documentation available on setting up a separate Kraft controller in the Apache Kafka documentation. You can refer to the following resources: - Kraft Controller Quorum <https://kafka.apache.org/documentation/#basic_ops_controller_quorum> - Kraft Configuration <https://kafka.apache.org/documentation/#kraft_configuration> On Tue, Apr 18, 2023 at 11:27 AM Doug Whitfield <dwhitfi...@perforce.com.invalid> wrote: > Hi folks, > > Is it possible to have a separate Kraft controller from the brokers? Is > there any documentation on setting this up? > > Thanks, > Doug Whitfield > > > This e-mail may contain information that is privileged or confidential. If > you are not the intended recipient, please delete the e-mail and any > attachments and notify us immediately. > >
