-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
1.4.0Version Server List 503 #4573
Comments
我尝试使用IP:PORT方式进行访问, 发现其中两个节点访问 服务列表 必然503 I tried to use the IP:PORT method to access, and found that two of the nodes access the service list must be 503 |
我试了一下 确实是会报有这个old raft stop的错误,但是不会返回503. 能看一下返回503的时候的错误信息吗? |
另外, 第二张截图的节点元数据,全部打开看一下,截图或者复制贴出来看一下 |
@dodolook8716 然后我又在物理机环境搭建了3台1.4.0版本的集群,也没有出现old raft stop的错误,和503的错误。
能麻烦提供一下这两个信息吗? 否则我们没法复现问题,只能关闭issue了 |
感谢你的关注. 我分别ip:port方式访问了三个节点, 通过devtool 将 |
@dodolook8716 方便吧3个节点的服务端日志全部打包上传一下吗? 服务端返回server is Down now,应该是raft选主没有成功,导致状态一直是非启动。 |
我用k8s搭建的 感觉rafe选举还是有些问题 不太确定和k8s网络是否有关系 有些节点正常 |
[root@nacos-4 nacos]# curl http://nacos-2.nacos-headless.kifs.svc.cluster.local:8848/nacos/v1/ns/raft/state |
raft的关键日志一般在 alipay-jraft.log , protocol-raft.log, naming-raft.log, nacos.log 把这几个文件上传一下吧。 几个节点都需要 |
我从1.3.1升级到1.4.1也遇到了这个问题 |
也遇到这个问题,新鲜出炉的日志 |
你好,这个问题有解决了么?我 k8s 1.17,nacos1.4.1也遇到了一样的问题。 |
我也是遇到了这个问题,生产出现故障多次了,更新pod后就会异常,nacos要重新部署才恢复 |
+1 |
我使用docker部署集群模式, 部署后已经手动删除~/data/protocol, 并进行了重启. 现在 服务注册发现在我的项目中没有问题, 我想通过WEB UI来观察当前提供服务的实例. 我需要在页面点击查询三次才能看到我想要的信息, 进入详情需要刷新三次才能看到我想要的信息.
I use docker to deploy the cluster mode. After deployment, I have manually deleted ~/data/protocol and restarted it. Now the service registration found that there is no problem in my project. I want to observe the current service instance through the WEB UI. I need Click the query three times on the page to see the information I want, and enter the details to refresh three times to see the information I want.
我分别观察各个实例的 nacos.log 发现 错误的请求总会引发出现这个异常
java.lang.IllegalStateException: old raft protocol already stop
而正确的请求没有这种情况.I observed the nacos.log of each instance and found that wrong requests always cause this exception
java.lang.IllegalStateException: old raft protocol already stop
, but correct requests do not have this situation.The text was updated successfully, but these errors were encountered: