apache / apache/logging-log4j2
lost log files under high load (using .gz)
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.7k
- Avg merge
- 21h 30m
- Merged PRs (30d)
- 27
Description
## Description
In our production, entries in log files are lost under high load.
It is possible that this is due to the archiving process.
It seems that if the file archiving of one file is not completed and the second one is already starting to archive, they can overwrite each other.
## Configuration
**Version:** [2.24.3]
**Operating system:** [Oracle Linux Server 8.4; win10]
**JDK:** [21]
## Reproduction
Most likely, the problem will reproduce well on weak servers, where the file archiving process takes some considerable time. For example, on servers with a slow HDD or with a slow CPU.
Simple test to reproduce here:
https://github.com/dasvex/log4j-lost-files-on-gz/tree/main
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked reproduction repository and the Log4j 2.24.3 file-archiving behavior described in the issue. Confirm whether overlapping .gz archiving causes entries to be lost under slow, high-load conditions; done means the reproduction no longer loses log files and the behavior is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100