[
https://issues.apache.org/jira/browse/KAFKA-9254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16986025#comment-16986025
]
fenghong edited comment on KAFKA-9254 at 12/2/19 12:38 PM:
-----------------------------------------------------------
We can reproduce this bug with the latest version (2.3.1) and this version
(2.0.1)
Need to continue writing data during testing
OS
{code:java}
Linux 4.15.0-70-generic #79~16.04.1-Ubuntu SMP Tue Nov 12 14:01:10 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
{code}
JAVA
{code:java}
java version "1.8.0_192"
Java(TM) SE Runtime Environment (build 1.8.0_192-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.192-b12, mixed mode)
{code}
Server.propertity
{code:java}
broker.id=4
delete.topic.enable=true
listeners=PLAINTEXT://xxx:9092
num.network.threads=9
num.io.threads=12
socket.send.buffer.bytes=102400
socket.receive.buffer.bytes=102400
socket.request.max.bytes=104857600
log.dirs=/data/data/kafka,/data2/data/kafka,/data3/data/kafka,/data4/data/kafka
num.partitions=1
num.recovery.threads.per.data.dir=2
offsets.topic.replication.factor=5
transaction.state.log.replication.factor=5
transaction.state.log.min.isr=3
log.retention.hours=26280
log.segment.bytes=10737418
log.retention.check.interval.ms=300000
zookeeper.connect=xxx1:2181,xxx2:2181,xxx3:2181,xxx4:2181,xxx5:2181
zookeeper.connection.timeout.ms=6000
zookeeper.session.timeout.ms=6000
group.initial.rebalance.delay.ms=500
default.replication.factor=3
min.insync.replicas=3
auto.create.topics.enable=false
unclean.leader.election.enable=false
log.cleanup.policy=delete
num.replica.fetchers=2
replica.lag.time.max.ms=10000
replica.fetch.wait.max.ms=500
{code}
was (Author: fenghong):
We can reproduce this bug with the latest version (2.3.1)
Need to continue writing data during testing
OS
{code:java}
Linux 4.15.0-70-generic #79~16.04.1-Ubuntu SMP Tue Nov 12 14:01:10 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
{code}
JAVA
{code:java}
java version "1.8.0_192"
Java(TM) SE Runtime Environment (build 1.8.0_192-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.192-b12, mixed mode)
{code}
Server.propertity
{code:java}
broker.id=4
delete.topic.enable=true
listeners=PLAINTEXT://xxx:9092
num.network.threads=9
num.io.threads=12
socket.send.buffer.bytes=102400
socket.receive.buffer.bytes=102400
socket.request.max.bytes=104857600
log.dirs=/data/data/kafka,/data2/data/kafka,/data3/data/kafka,/data4/data/kafka
num.partitions=1
num.recovery.threads.per.data.dir=2
offsets.topic.replication.factor=5
transaction.state.log.replication.factor=5
transaction.state.log.min.isr=3
log.retention.hours=26280
log.segment.bytes=10737418
log.retention.check.interval.ms=300000
zookeeper.connect=xxx1:2181,xxx2:2181,xxx3:2181,xxx4:2181,xxx5:2181
zookeeper.connection.timeout.ms=6000
zookeeper.session.timeout.ms=6000
group.initial.rebalance.delay.ms=500
default.replication.factor=3
min.insync.replicas=3
auto.create.topics.enable=false
unclean.leader.election.enable=false
log.cleanup.policy=delete
num.replica.fetchers=2
replica.lag.time.max.ms=10000
replica.fetch.wait.max.ms=500
{code}
> Topic level configuration failed
> --------------------------------
>
> 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
> 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)
