You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Ron Dagostino (Jira)" <ji...@apache.org> on 2021/11/23 13:37:00 UTC

[jira] [Updated] (KAFKA-13456) Tighten KRaft config checks/constraints

     [ https://issues.apache.org/jira/browse/KAFKA-13456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ron Dagostino updated KAFKA-13456:
----------------------------------
    Fix Version/s:     (was: 3.1.0)

> Tighten KRaft config checks/constraints
> ---------------------------------------
>
>                 Key: KAFKA-13456
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13456
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 2.8.0, 3.0.0
>            Reporter: Ron Dagostino
>            Assignee: Ron Dagostino
>            Priority: Major
>
> The controller.listener.names config is currently checked for existence when the process.roles contains the controller role (i.e. process.roles=controller or process.roles=broker,contrtoller); it is not checked for existence when process.roles=broker.  However, KRaft brokers have to talk to KRaft controllers, of course, and they do so by taking the first entry in the controller.listener.names list.  Therefore, controller.listener.names is required in KRaft mode even when process.roles=broker.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)