-
-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
客户端 notifications/v2 504 怎么解 #1045
Comments
你先浏览器访问以下这个URL看看?tomcat应该不会返回504吧? |
浏览器一样504。修改配置并发布后,重新访问(notificationId已请求过)正常,但使用新的notificationId 依然504 |
@mhcxp 您好,这个最终怎么解决了呢?我的也是这个问题,分布式部署方式 |
504应该是Long Polling不是通过IP直连config service,而是走了网关或nginx之类的,需要调大网关或nginx上的超时设置到1分钟以上。 |
case先关闭了,如还有问题,可以提供更多信息,或进群交流。 |
[Apollo-RemoteConfigLongPollService-1] WARN c.c.f.a.i.RemoteConfigLongPollService -【】- Long polling failed, will retry in 1 seconds. appId: hnf-orders-consumer-server, cluster: default, namespaces: application, long polling url: http://172.17.0.3:8180/notifications/v2?cluster=default&appId=hnf-orders-consumer-server&ip=10.244.1.3¬ifications=%5B%7B%22namespaceName%22%3A%22application%22%2C%22notificationId%22%3A88%7D%5D, reason: Could not complete get operation [Cause: No route to host (Host unreachable)] |
nginx keepalive_timeout 120; 还是同样报超时 HTTP response code: 504 |
+1 |
版本: 0.10.2
The text was updated successfully, but these errors were encountered: