Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.3.0
-
None
-
None
Description
I applied a dynamic configuration change using the following command:
kafka-configs --bootstrap-server `hostname`:9093 --command-config /etc/kafka/consumer.properties --entity-type brokers --entity-name 1 --alter --add-config log.cleaner.min.cleanable.ratio=0.00
I applied the change to each node in a 6 node cluster. This caused the log cleaner thread to die on each node. I reverted the config and restarted the broker to restore functionality.
Also interesting (although a bit of a digression) is that I was not able to restart the log cleaning thread without restarting the broker. I tried running:
kafka-configs --bootstrap-server `hostname`:9093 --command-config /etc/kafka/consumer.properties --entity-type brokers --entity-name 1 --alter --add-config log.cleaner.threads=3
The log-cleaner log file showed the threads starting, but they never actually starting cleaning topic partitions.
Attachments
Issue Links
- is related to
-
KAFKA-12613 Inconsistencies between Kafka Config and Log Config
- Resolved