[KAFKA-9254] Updating Kafka Broker configuration dynamically twice reverts log configuration to default

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.1.0, 2.0.1, 2.1.1, 2.2.2, 2.4.0, 2.3.1
• Fix Version/s: 1.1.2, 2.0.2, 2.1.2, 2.2.3, 2.3.2, 2.4.1
• Component/s: config, log, replication
• Assignee: huxihx
• Reporter: fenghong
• Created: 01/Dec/19 06:24
• Updated: 03/Mar/20 20:00
• Resolved: 25/Jan/20 01:24

Description

We are engineers at Huobi and now encounter Kafka BUG 

Modifying DynamicBrokerConfig more than 2 times will invalidate the topic level unrelated configuration

The bug reproduction method as follows：

1. Set Kafka Broker config  server.properties min.insync.replicas=3
2. Create topic test-1 and set topic‘s level config min.insync.replicas=2
3. Dynamically modify the configuration twice as shown below

bin/kafka-configs.sh --bootstrap-server xxx:9092 --entity-type brokers --entity-default --alter --add-config log.message.timestamp.type=LogAppendTime

bin/kafka-configs.sh --bootstrap-server xxx:9092 --entity-type brokers --entity-default --alter --add-config log.retention.ms=604800000

1. stop a Kafka Server and found the Exception as shown below
   org.apache.kafka.common.errors.NotEnoughReplicasException: Number of insync replicas for partition test-1-0 is [2], below required minimum [3]

 

 

Issue Links

• links to: GitHub Pull Request #7870
• links to: GitHub Pull Request #8067