KunioHaha opened a new issue, #9622: URL: https://github.com/apache/rocketmq/issues/9622
### 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 Centos release 7.9.2009 ### RocketMQ version 5.1.0 ### JDK Version 1.8.0_202 ### Describe the Bug BrokerControllerScheduledThread1 Blocked in slave broker, The broker will not appear in the cluster. java IO opration createNewFile or FileInputStream will be failed, and the Thread will be blocked. there are some logs in different slave broker, They have similar errors : broker1 <img width="1107" height="231" alt="Image" src="https://github.com/user-attachments/assets/283e91e6-e860-4afc-91a0-68606185ceff"; /> <img width="1107" height="283" alt="Image" src="https://github.com/user-attachments/assets/4670f62b-878c-4c62-8424-f4726db21493"; /> broker2 <img width="1106" height="234" alt="Image" src="https://github.com/user-attachments/assets/f6970ada-cdab-4944-8b69-446c5b093fc7"; /> <img width="1107" height="196" alt="Image" src="https://github.com/user-attachments/assets/f4b2b381-626e-4465-8153-dc8ff24ac59d"; /> broker3 <img width="1107" height="319" alt="Image" src="https://github.com/user-attachments/assets/c4733bb4-75d4-4b5b-b21b-981eab41ee4e"; /> ### Steps to Reproduce no steps ### What Did You Expect to See? The I/O operation should be released regardless of success or failure ### What Did You See Instead? Thread blocked ### 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
