susonglin opened a new issue, #7799: URL: https://github.com/apache/rocketmq/issues/7799
### Before Creating the Bug Report - [X] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq/discussions). - [X] I have searched the [GitHub Issues](https://github.com/apache/rocketmq/issues) and [GitHub Discussions](https://github.com/apache/rocketmq/discussions) of this repository and believe that this is not a duplicate. - [X] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ. ### Runtime platform environment linux ### RocketMQ version 4.7.1 ### JDK Version 1.8 ### Describe the Bug Broker task of cleaning up expired messages at 4 a.m. may saturate disk I/O, leading to message write failures. Therefore, I hope this task can be executed smoothly. Although I found these three configurable properties and adjusted them, the effect is not as expected // (default:10000) cleanResourceInterval = 60000 //（default:100） deleteCommitLogFilesInterval = 10000; // (default:100) deleteConsumeQueueFilesInterval = 10000      'Compute logical min offset' is executed twice, which may be the reason for increased disk read I/O. However, from the source code, I haven't found any optimization opportunities. How should I handle this?   ### Steps to Reproduce none ### What Did You Expect to See? solution ### What Did You See Instead? solution ### Additional Context _No response_ -- 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...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
