[jira] [Updated] (KAFKA-9254) Updating Kafka Broker configuration dynamically twice reverts log configuration to default

["Vikas Singh (Jira)" <ji...@apache.org>]

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

Vikas Singh updated KAFKA-9254:
-------------------------------
    Summary: Updating Kafka Broker configuration dynamically twice reverts log configuration to default  (was: Topic level configuration failed)

> Updating Kafka Broker configuration dynamically twice reverts log configuration to default
> ------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-9254
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9254
>             Project: Kafka
>          Issue Type: Bug
>          Components: config, log, replication
>    Affects Versions: 2.0.1
>            Reporter: fenghong
>            Assignee: huxihx
>            Priority: Critical
>
> 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：
>  # Set Kafka Broker config  server.properties min.insync.replicas=3
>  # Create topic test-1 and set topic‘s level config min.insync.replicas=2
>  # Dynamically modify the configuration twice as shown below
> {code:java}
> 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
> {code}
>  # 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]
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)