Kris20030907 commented on issue #9290: URL: https://github.com/apache/rocketmq/issues/9290#issuecomment-2765454502
> > However, once the machine where namesrv is located is disconnected from the Internet (TCP level), or the network fluctuates for a long time, or the firewall jitters, the application layer channel cannot be detected as abnormal and will not be disconnected. > > I don't think so! You can refrence to the code: [NettyRemotingClient.java](https://github.com/apache/rocketmq/blob/release-5.3.1/remoting/src/main/java/org/apache/rocketmq/remoting/netty/NettyRemotingClient.java#L540): > >  If there is an abnormality in the communication between the client and NS, the client will actively close the link. By default, the next NS will be selected to establish a connection. So，I don't think need NameServer health check. Makes sense! Maybe I'm overthinking it. I'll verify again later whether turning on the isClientCloseSocketIfTimeout switch can solve this problem when the network is abnormal. -- 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]
