-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
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
nacos uses vip+nginx load balancing to cause a client to appear UNAVAILABLE: Network closed for unknown reason #12297
Comments
It should be your nginx or vip will close the connection with an interval. Please make sure your nginx and vip transport by tcp but not http and https. And make sure them will not reuse and redistribution connection with any dimensions. I suggest you try to connect nacos server directly, if connect directly is ok. there must be some config problem in vip or nginx to close connection each 3 seconds. |
It is normal to use VIP or connect to one nacos service |
I hope you can help me. This problem has been bothering me for a long time |
I use this configuration in nginx work well. you can try it. If can't work well. I suggest you find out which configuration make the connection closed by nginx or vip by yourself. |
Thank you very much. I'll try it your way. |
No more response from author for a long time, and this problem seems new version has solved this problem. |
Describe the bug
nacos uses vip+nginx load balancing to cause a client to appear UNAVAILABLE: Network closed for unknown reason
This works when accessing specific nacos nodes, but does not work when load balancing via nginx
Is nacos http service stateless, and if so, what about grpc
UNAVAILABLE: Network closed for unknown reason appears once every 3 seconds
hosts.conf
192.168.4.151 yanfa-nacos1
192.168.4.145 yanfa-nacos2
192.168.4.146 yanfa-nacos3
Desktop (please complete the following information):
Additional context
![image](https://private-user-images.githubusercontent.com/33612347/343796630-0d370221-6be1-42e7-8e19-cd6b7981305e.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQxMTA5MjIsIm5iZiI6MTcyNDExMDYyMiwicGF0aCI6Ii8zMzYxMjM0Ny8zNDM3OTY2MzAtMGQzNzAyMjEtNmJlMS00MmU3LThlMTktY2Q2Yjc5ODEzMDVlLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MTklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODE5VDIzMzcwMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWNlZjUyMGY4YzBmMjIwMzkyMTQ5MjMxY2I0MjgyZDRmYjVjOTliNTNkNDMyZTM3ZjZkMWQwM2NhODcyMmZlY2YmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.ZjvnGXtWNhvQHPFgnxe3cnMbcawUuXnicjmkILFH_Fg)
The text was updated successfully, but these errors were encountered: