humkum opened a new issue, #7902: URL: https://github.com/apache/rocketmq/issues/7902
### 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 CentOS7.3 ### RocketMQ version branch develop ### JDK Version Open_JDK 1.8.0_202 ### Describe the Bug In [ReputMessageService](https://github.com/apache/rocketmq/blob/develop/store/src/main/java/org/apache/rocketmq/store/DefaultMessageStore.java#L2929), we only catch Exception, which would make the doReput thread quit if there are Error throwing. ### Steps to Reproduce There are memory error or disk error occurred, the messages are putted to broker could not be consumed, because of the reput thread quit. ### What Did You Expect to See? The reput thread could catch these Error and should not quit abnormally. ### What Did You See Instead? The reput thread quit, and consumer cannot consume, consume lag is growing.  ### 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