Hi guys, RocketMQ follows the paradigm of long connections. Aka, the connections will be multiplexed for multiple remoting commands. This mechanism works well for regular cases. Unfortunately, when it comes to the server-offline use case, clients are frequently interrupted, witnessing a number of errors, and exceptions before the offline servers are passively detected and removed.
As a matter of fact, all paradigms of long connections would witness the same issue, for example, HTTP 2.0. And this is also the reason why it has a GOAWAY frame https://datatracker.ietf.org/doc/html/rfc7540#section-6.8 I've scratched a RIP: https://docs.google.com/document/d/1yoNtFFz91z1_SEkmadCURJL2-EdrNkG-3pFrzXnrz-k/edit?usp=sharing Let me know what you think. Zhanhui Li
