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

Posted to jira@kafka.apache.org by "Vinoth (Jira)" <ji...@apache.org> on 2023/03/10 04:11:00 UTC

[jira] [Assigned] (KAFKA-10807) AlterConfig should be validated by the target broker

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

Vinoth reassigned KAFKA-10807:
------------------------------

    Assignee: Vinoth

> AlterConfig should be validated by the target broker
> ----------------------------------------------------
>
>                 Key: KAFKA-10807
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10807
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Boyang Chen
>            Assignee: Vinoth
>            Priority: Major
>
> After forwarding is enabled, AlterConfigs will no longer be sent to the target broker. This behavior bypasses some important config change validations, such as path existence, static config conflict, or even worse when the target broker is offline, the propagated result does not reflect a true applied result. We should gather those necessary cases, and decide whether to actually handle the AlterConfig request firstly on the target broker, and then forward, in a validate-forward-apply path.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)