change pulsar.log.level in log4j2.yaml not work?
- Dominant language
- Java
- Stars
- 15.3k
- Forks
- 3.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 160
Description
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:

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`.

That's not what we expected.
**Version**
- pulsar version: 2.7.2
- log4j2 version: 2.17.1
Does anyone have the same problem?
Contributor guide
Research direction
Start with conf/log4j2.yaml and inspect how monitorInterval and the pulsar.log.root.level and pulsar.log.level properties are configured. Reproduce the change on Pulsar 2.7.2 and observe broker output after the reload interval. Done means determining whether the configured level is applied dynamically and recording or correcting the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100