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/17 14:24:00 UTC
[jira] [Updated] (KAFKA-13552) Unable to dynamically change broker log levels on KRaft
[ https://issues.apache.org/jira/browse/KAFKA-13552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ron Dagostino updated KAFKA-13552:
----------------------------------
Description:
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. The ticket for this particular spect of the issue is https://issues.apache.org/jira/browse/KAFKA-13502
was:
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.
> 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.1.0, 3.0.0
> Reporter: Ron Dagostino
> Priority: Major
>
> 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. The ticket for this particular spect of the issue is https://issues.apache.org/jira/browse/KAFKA-13502
--
This message was sent by Atlassian Jira
(v8.20.1#820001)