kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kamal Chandraprakash <kamal.chandraprak...@gmail.com>
Subject Re: Restart process after adding control.plane.listener.name config in Kafka 2.2.0
Date Mon, 06 May 2019 10:51:19 GMT
Migration plan for this change is mentioned in the KIP-291
<https://cwiki.apache.org/confluence/display/KAFKA/KIP-291%3A+Separating+controller+connections+and+requests+from+the+data+plane>.
Take a look at the migration plan.

Migration plan: 2 rounds of rolling upgrades are needed to pick up the
> proposed changes in this KIP. The goal of the first round is to add the
> controller endpoint, without adding the "control.plane.listener.name"
> config. Specifically, an endpoint with the controller listener name should
> be added to the "listeners" config, e.g. "CONTROLLER://192.1.1.8:9091";
> if the "advertised.listeners" config is explicitly configured and is not
> getting its value from "listeners", the new endpoint for controller should
> also be added to "advertised.listeners". After the first round is
> completed, controller to brokers communication should still behave in the
> same way that uses the inter-broker-listener-name, since the "
> control.plane.listener.name" is not set yet. In the 2nd round, the "
> control.plane.listener.name" config should be set to the corresponding
> listener name, e.g. "CONTROLLER". During rolling upgrade of the 2nd round,
> controller to brokers traffic will start using the "
> control.plane.listener.name", and go through the proposed changes in this
> KIP.


On Fri, May 3, 2019 at 5:28 PM Jonathan Santilli <jonathansantilli@gmail.com>
wrote:

> Hello, hope you all are great,
>
> I would like to know what's the process to update the Kafka Broker
> configuration in order to use the new config: *control.plane.listener.name
> <http://control.plane.listener.name> in Kafka version 2.2.0*
>
> The documentation says: *Name of listener used for communication between
> controller and brokers.*
>
> If I change it just in one Broker and restart it, will this cause a
> communication issue since the others Brokers still are not using the new
> config/port?
>
>
> Cheers!
> --
> Santilli Jonathan
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message