[
https://issues.apache.org/jira/browse/KAFKA-13552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461476#comment-17461476
]
Ron Dagostino commented on KAFKA-13552:
---------------------------------------
[~dengziming] Thanks for pointing that out. Although there is not much in that
ticket, it appears to address controller-only nodes, whereas this ticket
indicates that no KRaft node (broker-only, controller-only, or combined
broker+controller) supports dynamic changes to the log levels . I updated the
description of this ticket to point to that one since it is just one aspect of
the problem.
> 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)
