THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Configuration Name | Possible Values | Description | |||
|---|---|---|---|---|---|
| process.roles | null broker controller broker,controller | If this is null (absent) then we are in legacy mode. Otherwise, we are in KIP-500 mode and this configuration determines what roles this process should play: broker, controller, or both. | |||
| controller.listenerslistener.names | If non-null, this must be a comma-separated list of listener names. | A comma-separated list of the names of the listeners used by the KIP-500 controller. This is required if this process is a KIP-500 controller. The legacy controller will not use this configuration Despite the similar name, note that this is different from the "control plane listener" introduced by KIP-291. The "control plane listener" is used on brokers, not on controllers. | |||
| controller.connect | If non-null, this must be a comma-separated list of controller endpoints, in the format: {controller-id}@{controller-host):{controller-port} | When in KIP-500 mode, each node must have this configuration, in order to find out how to communicate with the controller quorum. | controller.connect.security.protocol | If non-null, this must be a security protocol such as PLAINTEXT, SSL, etc. | When in KIP-500 mode, this describes the security protocol that the broker should use to connect to the controllers. This defaults to PLAINTEXT if no value is given . |
| controller.id | a 32-bit ID | The controller id for this server. If this is not specified, we will default to the broker.id plus 3000. | |||
| registration.heartbeat.interval.ms | 2000 | The length of time between broker heartbeats. | |||
| registration.lease.timeout.ms | 18000 | The length of time that a broker lease lasts if no heartbeats are made. |
...