We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I found a bug, not just asking a question, which should be created in GitHub Discussions.
I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
OS:Linux
5.3.0
No response
broker logback配置不恰当,pop.log未开启日志轮转的压缩,其打日志频率极高,所以很容易占用过多的磁盘空间。未压缩时按照当前配置最多会占用20*128MB=2.5GB空间。
如果gunzip压缩,实测单个128MB的文件可以降到2.1MB,那pop.log占用空间上限=128MB+19*2.1MB=167.9MB
5.3.0的broker启动一段时间就能复现,otherdays中的日志情况如下: 手动压缩后可以减少不少空间
保持和其他日志文件的配置一样
N/a
The text was updated successfully, but these errors were encountered:
[ISSUE apache#8756] fix broker logback config, gzip the archive files.
d5a2e7a
Successfully merging a pull request may close this issue.
Before Creating the Bug Report
I found a bug, not just asking a question, which should be created in GitHub Discussions.
I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Runtime platform environment
OS:Linux
RocketMQ version
5.3.0
JDK Version
No response
Describe the Bug
broker logback配置不恰当,pop.log未开启日志轮转的压缩,其打日志频率极高,所以很容易占用过多的磁盘空间。未压缩时按照当前配置最多会占用20*128MB=2.5GB空间。
如果gunzip压缩,实测单个128MB的文件可以降到2.1MB,那pop.log占用空间上限=128MB+19*2.1MB=167.9MB
Steps to Reproduce
5.3.0的broker启动一段时间就能复现,otherdays中的日志情况如下:
手动压缩后可以减少不少空间
What Did You Expect to See?
保持和其他日志文件的配置一样
What Did You See Instead?
N/a
Additional Context
No response
The text was updated successfully, but these errors were encountered: