apache/pulsar

change pulsar.log.level in log4j2.yaml not work?

Open

#14,298 opened on Feb 15, 2022

View on GitHub
 (10 comments) (1 reaction) (0 assignees)Java (3,485 forks)batch import
Stalehelp wantedlifecycle/staletype/bug

Repository metrics

Stars
 (13,697 stars)
PR merge metrics
 (Avg merge 3d 10h) (146 merged PRs in 30d)

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, 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
Investigate why log4j2's monitorInterval does not trigger reload for pulsar.log.level when modifying conf/log4j2.yaml. Check if Pulsar's logging configuration uses SystemProperties or custom configuration that bypasses log4j2's automatic reloading.
Tech stack
java
Domain
backendobservability
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
JavaLog4j2
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60