We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1、如果是两个实例的服务端,前面挂一个负载均衡。这时候如果我滚动更新服务端,先重启A,这时候tcp连接断开,所有流量打在B上,B再重启,所有流量又打在了A上。就会出现一个服务器饥饿的问题。这种情况qrpc或者其他的rpc有没有解决办法呢?比如tcp连接定时断开重连之类的方案
2、如果由于某些原因,导致客户端和服务端的tcp连接断开,这里是怎么处理的呢
The text was updated successfully, but these errors were encountered:
1、如果是两个实例的服务端,前面挂一个负载均衡。这时候如果我滚动更新服务端,先重启A,这时候tcp连接断开,所有流量打在B上,B再重启,所有流量又打在了A上。就会出现一个服务器饥饿的问题。这种情况qrpc或者其他的rpc有没有解决办法呢?比如tcp连接定时断开重连之类的方案 2、如果由于某些原因,导致客户端和服务端的tcp连接断开,这里是怎么处理的呢
Sorry, something went wrong.
No branches or pull requests
1、如果是两个实例的服务端,前面挂一个负载均衡。这时候如果我滚动更新服务端,先重启A,这时候tcp连接断开,所有流量打在B上,B再重启,所有流量又打在了A上。就会出现一个服务器饥饿的问题。这种情况qrpc或者其他的rpc有没有解决办法呢?比如tcp连接定时断开重连之类的方案
2、如果由于某些原因,导致客户端和服务端的tcp连接断开,这里是怎么处理的呢
The text was updated successfully, but these errors were encountered: