sunwuxiang opened a new issue, #8997: URL: https://github.com/apache/rocketmq/issues/8997
### 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 and windows ### RocketMQ version 4.7.1 ### JDK Version jdk11 ### Describe the Bug <img width="580" alt="b2489c47defcd7426ba819008233748" src="https://github.com/user-attachments/assets/f9956b46-f3c0-45e0-8969-110e50bbcf16";> broker-f 突然内存持续上涨，导致服务假死，也未从nameserver摘掉，导致客户端连接超时，虽然mq有三次重试，通过上图发现后两次请求到了正常的broker，应该成功，结果还是失败了 <img width="588" alt="7a5b9cf09a1974768c6bf495e0f801c" src="https://github.com/user-attachments/assets/6bc4a795-b5de-4141-8300-ec781581dee6";> ### Steps to Reproduce 现在我们无法复现broker内存上涨假死的情况，可以制造一个broker访问不通使得连接把耗时耗光 ### What Did You Expect to See? 期望的是，单个请求超时和整体三次重试的超时分开配置 ### What Did You See Instead? 期望的是，单个请求超时和整体三次重试的超时分开配置 ### Additional Context 无 -- 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
