-
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
[NA] failed to update serviceName: DEFAULT_GROUP@@prod-zipkin #3876
Comments
What's your version of nacos-server? |
nacos-server的版本是 1.3.1 |
Is the 'zipkin' blocked due to network problems? I think you should check whether health check fails. |
没太看明白您的意思呢?我的服务中是没有zipkin的,但是不知道为什么客户端获取到了zipkin,并且还要对他进行更新,并且按理说就算是更新也不会报错。 |
这其实是两个问题
关于第二个问题,可能需要您帮我们调用一下api,看下返回值是什么
|
返回值是: |
我从没有出现过这个问题。。 也没有想到什么情况下会出现这个问题。只能先看看如何复现出来。。 |
请贴出你的项目的配置文件,以及seluth的版本信息 |
sleuth是2.1.1RELEASE actuator暴露监控端点management: feign 配置feign: hystrix 配置hystrix: #请求处理的超时时间 |
我也出现了同样的问题,我们有evaluate这个服务 |
it may be caused by InstanceController line 755 of 1.4.0. |
@i will solve it@ |
I think @KomachiSion is right. The 1.4.0 logic is as following:
If the isCheck=true, this code part will be executed
In this case, the client get an empty json response, and in the following HostReactor.java code part, throws NullPointerException.
To solve this problem, There are two ways: 1. modify server code
After deleting it, the logic will be, if the protection threshold is reached, return all of the ips(including healthy and unhealthy instances). In this way, the a part of the QPS are going to the unhealthy instances and lost, but the healthy instances are protected.
to
|
PR#4864 correspond to solution 1, modify server code |
Describe the bug
服务中没有zipkin,但是偶尔会报错,无法更新zipkin这个服务,报错信息:
[NA] failed to update serviceName: DEFAULT_GROUP@@prod-zipkin.xxxxx.com java.lang.NullPointerException: null at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936) at com.alibaba.nacos.client.naming.core.HostReactor.processServiceJson(HostReactor.java:128) at com.alibaba.nacos.client.naming.core.HostReactor.updateServiceNow(HostReactor.java:333) at com.alibaba.nacos.client.naming.core.HostReactor$UpdateTask.run(HostReactor.java:397) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: