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

Divij Vaidya updated KAFKA-15341:
---------------------------------
    Description: 
When we are in a rolling restart to enable TS at system level, some brokers 
have TS enabled on them and some don't. We send an alter config call to enable 
TS for a topic, it hits a broker which has TS enabled, this broker forwards it 
to the controller and controller will send the config update to all brokers. 
When another broker which doesn't have TS enabled (because it hasn't undergone 
the restart yet) gets this config change, it "should" fail to apply it. But 
failing now is too late since alterConfig has already succeeded since 
controller->broker config propagation is done async.

With this JIRA, we want to have controller check if TS is enabled on all 
brokers before applying alter config to turn on TS for a topic.

Context: https://github.com/apache/kafka/pull/14176#discussion_r1291265129

  was:
When we are in a rolling restart to enable TS at system level, some brokers 
have TS enabled on them and some don't. We send an alter config call to enable 
TS for a topic, it hits a broker which has TS enabled, this broker forwards it 
to the controller and controller will send the config update to all brokers. 
When another broker which doesn't have TS enabled (because it hasn't undergone 
the restart yet) gets this config change, it "should" fail to apply it. But 
failing now is too late since alterConfig has already succeeded since 
controller->broker config propagation is done async.

With this JIRA, we want to have controller check if TS is enabled on all 
brokers before applying alter config to turn on TS for a topic.


> Enabling TS for a topic during rolling restart causes problems
> --------------------------------------------------------------
>
>                 Key: KAFKA-15341
>                 URL: https://issues.apache.org/jira/browse/KAFKA-15341
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Divij Vaidya
>            Priority: Major
>             Fix For: 3.6.0
>
>
> When we are in a rolling restart to enable TS at system level, some brokers 
> have TS enabled on them and some don't. We send an alter config call to 
> enable TS for a topic, it hits a broker which has TS enabled, this broker 
> forwards it to the controller and controller will send the config update to 
> all brokers. When another broker which doesn't have TS enabled (because it 
> hasn't undergone the restart yet) gets this config change, it "should" fail 
> to apply it. But failing now is too late since alterConfig has already 
> succeeded since controller->broker config propagation is done async.
> With this JIRA, we want to have controller check if TS is enabled on all 
> brokers before applying alter config to turn on TS for a topic.
> Context: https://github.com/apache/kafka/pull/14176#discussion_r1291265129



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

Reply via email to