Stephane Maarek created KAFKA-7355: -------------------------------------- Summary: Topic Configuration Changes are not applied until reboot Key: KAFKA-7355 URL: https://issues.apache.org/jira/browse/KAFKA-7355 Project: Kafka Issue Type: Bug Components: config, core Affects Versions: 2.0.0 Reporter: Stephane Maarek
Steps to reproduce: {code} kafka-topics --zookeeper 127.0.0.1:2181 --create --topic employee-salary --partitions 1 --replication-factor 1 kafka-configs --zookeeper 127.0.0.1:2181 --alter --entity-type topics --entity-name employee-salary --add-config cleanup.policy=compact,min.cleanable.dirty.ratio=0.001,segment.ms=5000 kafka-configs --zookeeper 127.0.0.1:2181 --alter --entity-type topics --entity-name employee-salary kafka-console-producer --broker-list 127.0.0.1:9092 --topic employee-salary --property parse.key=true --property key.separator=, {code} Try publishing a bunch of data, and no segment roll over will happen (even though segment.ms=5000). I looked at the kafka directory and the kafka logs to ensure I noticed the broker processed the notification of config changes, but the behaviour was not updated to use the new config values nonetheless. After restarting the broker, the expected behaviour is observed -- This message was sent by Atlassian JIRA (v7.6.3#76005)