[
https://issues.apache.org/jira/browse/KAFKA-8926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jordan Mcmillan updated KAFKA-8926:
-----------------------------------
Description:
I applied a dynamic configuration change using the following command:
{code:bash}
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
{code}
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:
{code:bash}
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
{code}
The log-cleaner log file showed the threads starting, but they never actually
starting cleaning topic partitions.
was:
I applied a dynamic configuration change using the following command:
{code:bash}
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
{code}
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 starting the broker. I tried running:
{code:bash}
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
{code}
The log-cleaner log file showed the threads starting, but they never actually
starting cleaning topic partitions.
> Log Cleaner thread dies when log.cleaner.min.cleanable.ratio is set to 0
> ------------------------------------------------------------------------
>
> Key: KAFKA-8926
> URL: https://issues.apache.org/jira/browse/KAFKA-8926
> Project: Kafka
> Issue Type: Bug
> Components: log cleaner
> Affects Versions: 2.3.0
> Reporter: Jordan Mcmillan
> Priority: Major
>
> I applied a dynamic configuration change using the following command:
> {code:bash}
> 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
> {code}
> 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:
> {code:bash}
> 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
> {code}
> The log-cleaner log file showed the threads starting, but they never actually
> starting cleaning topic partitions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
