You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Ron Dagostino (Jira)" <ji...@apache.org> on 2021/12/16 23:09:00 UTC
[jira] [Created] (KAFKA-13552) Unable to dynamically change broker log levels on KRaft
Ron Dagostino created KAFKA-13552:
-------------------------------------
Summary: Unable to dynamically change broker log levels on KRaft
Key: KAFKA-13552
URL: https://issues.apache.org/jira/browse/KAFKA-13552
Project: Kafka
Issue Type: Bug
Components: kraft
Affects Versions: 3.0.0, 3.1.0
Reporter: Ron Dagostino
It is currently not possible to dynamically change the log level in KRaft. For example:
kafka-configs.sh --bootstrap-server <address> --alter --add-config "kafka.server.ReplicaManager=DEBUG" --entity-type broker-loggers --entity-name 0
Results in:
org.apache.kafka.common.errors.InvalidRequestException: Unexpected resource type BROKER_LOGGER.
The code to process this request is in ZkAdminManager.alterLogLevelConfigs(). This needs to be moved out of there, and the functionality has to be processed locally on the broker instead of being forwarded to the KRaft controller.
It is also an open question as to how we can dynamically alter log levels for a remote KRaft controller. Connecting directly to it is one possible solution, but that may not be desirable since generally connecting directly to the controller is not necessary.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)