[GitHub] [pulsar] ethqunzhong opened a new issue #14298: change pulsar.log.level in log4j2.yaml not work?

[GitBox]

ethqunzhong opened a new issue #14298:
URL: https://github.com/apache/pulsar/issues/14298


   change pulsar.log.level in log4j2.yaml not work?
   
   **Describe the bug**
   i modify the value of `pulsar.log.root.level` and `pulsar.log.level` from 
`info` to `warn` in `conf/log4j2.yaml` without restart broker service. 
   as follow:
   <img width="336" alt="image" 
src="https://user-images.githubusercontent.com/16517186/154048409-e4c3acd6-5e79-4293-842c-a1ff95ca2c45.png";>
   
   as this issue discribe [Add ability to log at a dynamic 
level](https://jira.qos.ch/browse/SLF4J-124), log4j2.x support reload conf with 
process restart.so as expected behavior, after monitorInterval later, broker 
service log's log level should be not lower than `warn`.but in fact,  latest 
output log still is `info`. 
   <img width="1071" alt="image" 
src="https://user-images.githubusercontent.com/16517186/154051892-f45088cb-e5d5-4a4d-8867-293705d523a5.png";>
   
   That's not what we expected.
   
   
   **Version**
   
    - pulsar version: 2.7.2
    - log4j2 version: 2.17.1
   
   
   Does anyone have the same problem?
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org