Skip to content
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

自动断开重新注册问题 #252

Open
china9839 opened this issue Jun 17, 2023 · 7 comments
Open

自动断开重新注册问题 #252

china9839 opened this issue Jun 17, 2023 · 7 comments

Comments

@china9839
Copy link

2023-06-17 10:07:43.436 [Warning] [Nacos.V2.Naming.NacosNamingService] Grpc connection disconnect, mark to redo
2023-06-17 10:07:43.436 [Warning] [Nacos.V2.Naming.NacosNamingService] mark to redo completed
2023-06-17 10:07:43.436 [Information] [Nacos.V2.Naming.NacosNamingService] Grpc connection connect
2023-06-17 10:07:48.423 [Information] [Nacos.V2.Naming.NacosNamingService] Redo instance operation REGISTER for "DEFAULT_GROUP"@@"system-service"
2023-06-17 10:07:48.424 [Information] [Nacos.V2.Naming.NacosNamingService] Redo instance operation REGISTER for "DEFAULT_GROUP"@@"system-service"
2023-06-17 10:07:48.431 [Information] [Nacos.V2.Naming.NacosNamingService] Redo subscriber operation

@china9839
Copy link
Author

应用是.net core3.1 webapi ,Nacos sdk用的是1.2.1版本
系统运行一段时间就会报上边的警告信息,这时这个服务从nacos就请求不进来了

@catcherwong
Copy link
Collaborator

这个是触发了客户端和服务端的重连机制,做完全 redo 的操作后,服务是会重新注册和被发现的。

@china9839
Copy link
Author

这个是触发了客户端和服务端的重连机制,做完全 redo 的操作后,服务是会重新注册和被发现的。

嗯,大概了解。那么grpc长连接 每5秒钟向nacos发送心跳,假设nacos服务一直正常。那么上边这个问题,有可能是grpcclient链接无法创建,或调用不可达的情况发生吗?

@china9839
Copy link
Author

这个是触发了客户端和服务端的重连机制,做完全 redo 的操作后,服务是会重新注册和被发现的。

主要是什么情况下,能触发这个redo那。
而且redo之后,好像nacos重新注册,有段时间从nacos是调不进来服务的

@ROMYIM
Copy link

ROMYIM commented Dec 14, 2023

@catcherwong @china9839 我的服务现在也会出现这个问题。突然间就断掉了。而且一直重连失败,要重启容器才行,不知道为什么。nacos-sdk包用的是1.3.5

@catcherwong
Copy link
Collaborator

@ROMYIM 有具体的日志吗?

@liangdan862679370
Copy link

@ROMYIM 有具体的日志吗?

我的问题和他类似用也是1.3.5,nacos版本2.1.1,连接成功后几秒就断了,我看是心跳检测不过,具体日志
[19:30:54.673 scm-std-message-apis-55b4659cc-9m67s Information] [QuantumBootstraper] Host Build Success, Start Run...

[19:30:59.732 scm-std-message-apis-55b4659cc-9m67s Error] [Nacos.V2.Naming.NacosNamingService] [SecurityProxy] login http request failed, url: http://svc-scm-nacos-headless:8848/nacos/v1/auth/users/login

System.Threading.Tasks.TaskCanceledException: The operation was canceled.

at System.Net.Http.ConnectHelper.ConnectAsync(String host, Int32 port, CancellationToken cancellationToken)

at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean allowHttp2, CancellationToken cancellationToken)

at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, CancellationToken cancellationToken)

at System.Net.Http.HttpConnectionPool.GetHttpConnectionAsync(HttpRequestMessage request, CancellationToken cancellationToken)

at System.Net.Http.HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage request, Boolean doRequestAuth, CancellationToken cancellationToken)

at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)

at System.Net.Http.HttpClient.FinishSendAsyncBuffered(Task`1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts)

at Nacos.V2.Security.SecurityProxy.LoginAsync(String server)

[19:30:59.732 scm-std-message-apis-55b4659cc-9m67s Error] [Nacos.V2.Naming.NacosNamingService] [SecurityProxy] login http request failed, url: http://svc-scm-nacos-headless:8848/nacos/v1/auth/users/login

System.Threading.Tasks.TaskCanceledException: The operation was canceled.

at System.Net.Http.ConnectHelper.ConnectAsync(String host, Int32 port, CancellationToken cancellationToken)

at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean allowHttp2, CancellationToken cancellationToken)

at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, CancellationToken cancellationToken)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants