You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
The data in the Nacos 2.1.2 cluster is not synchronized(Nacos 2.1.2 集群数据不同步)
#15974
Env info:Nacos server 2.1.2 (3-node StatefulSet with PVC persistence), deployed using the nacos helm chart 0.15 (based on Chart.yml), with member address format as Pod FQDN (PREFER_HOST_MODE=hostname), and without authentication enabled.
Nacos server 2.1.2(3 节点 StatefulSet,PVC 持久化),使用 nacos helm chart 0.15(源自Chart.yml) 部署,成员地址形态为 Pod FQDN(PREFER_HOST_MODE=hostname),未开鉴权。
I attempted to remove and deactivate the application instance through the Nacos API (http://${NACOS_HOST}/nacos/v1/ns/instance?serviceName=${SVC}&groupName=${GROUP}&namespaceId=${NS}&ip=${IP}&port=${PORT}&enabled=false). After doing so, the Nacos console showed that the status of this application instance alternated between online and offline.
我在尝试通过 nacos api 对 application instance 摘流下线(http://${NACOS_HOST}/nacos/v1/ns/instance?serviceName=${SVC}&groupName=${GROUP}&namespaceId=${NS}&ip=${IP}&port=${PORT}&enabled=false)后,Nacos 控制台显示该application instance 的状态为时而上线时而下线;
So I verified the consistency of the application instance data on 3 Nacos nodes through the script, and found that there were inconsistencies.于是我通过脚本验证 3 个nacos节点上的应用实例数据的一致性,发现不一致。
Desktop (please complete the following information):
提问
The cluster is running normally with no error logs.
Is this issue a defect in Nacos version 2.1.2, a chart version flaw, a deployment method problem, or have I missed any operational steps? How can we resolve this issue in a Kubernetes Nacos cluster? Any other suggestions would be appreciated.
Thanks for support .
集群运行正常,日志无报错。
该问题是nacos 2.1.2 版本缺陷、还是 chart 版本缺陷、还是部署方式的问题,或者是我遗漏了什么操作步骤?如何解决 k8s 中 nacos 集群的这个问题?以及其他建议。
谢谢。
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Env info:Nacos server 2.1.2 (3-node StatefulSet with PVC persistence), deployed using the nacos helm chart 0.15 (based on Chart.yml), with member address format as Pod FQDN (PREFER_HOST_MODE=hostname), and without authentication enabled.
Nacos server 2.1.2(3 节点 StatefulSet,PVC 持久化),使用 nacos helm chart 0.15(源自Chart.yml) 部署,成员地址形态为 Pod FQDN(PREFER_HOST_MODE=hostname),未开鉴权。
我在尝试通过 nacos api 对 application instance 摘流下线(http://${NACOS_HOST}/nacos/v1/ns/instance?serviceName=${SVC}&groupName=${GROUP}&namespaceId=${NS}&ip=${IP}&port=${PORT}&enabled=false)后,Nacos 控制台显示该application instance 的状态为时而上线时而下线;
Result 结果:
{ "code": 200, "message": null, "data": [ { "ip": "nacos-0.nacos-hs.nacos.svc.cluster.local", "port": 8848, "state": "UP", "extendInfo": { "lastRefreshTime": 1793350840938, "raftMetaData": { "metaDataMap": { "naming_instance_metadata": { "raftGroupMember": [ "nacos-0.nacos-hs.nacos.svc.cluster.local:7848" ] }, "naming_persistent_service": { "leader": "nacos-0.nacos-hs.nacos.svc.cluster.local:7848", "raftGroupMember": [ "nacos-0.nacos-hs.nacos.svc.cluster.local:7848" ], "term": 79 }, "naming_persistent_service_v2": { "leader": "nacos-0.nacos-hs.nacos.svc.cluster.local:7848", "raftGroupMember": [ "nacos-0.nacos-hs.nacos.svc.cluster.local:7848" ], "term": 79 }, "naming_service_metadata": { "leader": "nacos-0.nacos-hs.nacos.svc.cluster.local:7848", "raftGroupMember": [ "nacos-0.nacos-hs.nacos.svc.cluster.local:7848" ], "term": 79 } } }, "raftPort": "7848", "readyToUpgrade": true, "version": "2.1.2" }, "address": "nacos-0.nacos-hs.nacos.svc.cluster.local:8848", "failAccessCnt": 0, "abilities": { "remoteAbility": { "supportRemoteConnection": true }, "configAbility": { "supportRemoteMetrics": false }, "namingAbility": { "supportJraft": true } } }, { "ip": "nacos-1.nacos-hs.nacos.svc.cluster.local", "port": 8848, "state": "UP", "extendInfo": { "lastRefreshTime": 1793350840795, "raftMetaData": { "metaDataMap": { "naming_instance_metadata": { "leader": "nacos-0.nacos-hs.nacos.svc.cluster.local:7848", "raftGroupMember": [ "nacos-1.nacos-hs.nacos.svc.cluster.local:7848", "nacos-2.nacos-hs.nacos.svc.cluster.local:7848", "nacos-0.nacos-hs.nacos.svc.cluster.local:7848" ], "term": 81 }, "naming_persistent_service": { "raftGroupMember": [ "nacos-0.nacos-hs.nacos.svc.cluster.local:7848" ] }, "naming_persistent_service_v2": { "leader": "nacos-0.nacos-hs.nacos.svc.cluster.local:7848", "raftGroupMember": [ "nacos-1.nacos-hs.nacos.svc.cluster.local:7848", "nacos-2.nacos-hs.nacos.svc.cluster.local:7848", "nacos-0.nacos-hs.nacos.svc.cluster.local:7848" ], "term": 79 }, "naming_service_metadata": { "raftGroupMember": [ "nacos-0.nacos-hs.nacos.svc.cluster.local:7848" ] } } }, "raftPort": "7848", "readyToUpgrade": true, "version": "2.1.2" }, "address": "nacos-1.nacos-hs.nacos.svc.cluster.local:8848", "failAccessCnt": 0, "abilities": { "remoteAbility": { "supportRemoteConnection": true }, "configAbility": { "supportRemoteMetrics": false }, "namingAbility": { "supportJraft": true } } }, { "ip": "nacos-2.nacos-hs.nacos.svc.cluster.local", "port": 8848, "state": "UP", "extendInfo": { "lastRefreshTime": 1793350774630, "raftMetaData": { "metaDataMap": { "naming_instance_metadata": { "leader": "nacos-0.nacos-hs.nacos.svc.cluster.local:7848", "raftGroupMember": [ "nacos-1.nacos-hs.nacos.svc.cluster.local:7848", "nacos-2.nacos-hs.nacos.svc.cluster.local:7848", "nacos-0.nacos-hs.nacos.svc.cluster.local:7848" ], "term": 81 }, "naming_persistent_service": { "leader": "nacos-0.nacos-hs.nacos.svc.cluster.local:7848", "raftGroupMember": [ "nacos-1.nacos-hs.nacos.svc.cluster.local:7848", "nacos-2.nacos-hs.nacos.svc.cluster.local:7848", "nacos-0.nacos-hs.nacos.svc.cluster.local:7848" ], "term": 79 }, "naming_persistent_service_v2": { "raftGroupMember": [ "nacos-1.nacos-hs.nacos.svc.cluster.local:7848", "nacos-0.nacos-hs.nacos.svc.cluster.local:7848", "nacos-2.nacos-hs.nacos.svc.cluster.local:7848" ] }, "naming_service_metadata": { "leader": "nacos-0.nacos-hs.nacos.svc.cluster.local:7848", "raftGroupMember": [ "nacos-1.nacos-hs.nacos.svc.cluster.local:7848", "nacos-2.nacos-hs.nacos.svc.cluster.local:7848", "nacos-0.nacos-hs.nacos.svc.cluster.local:7848" ], "term": 79 } } }, "raftPort": "7848", "readyToUpgrade": true, "version": "2.1.2" }, "address": "nacos-2.nacos-hs.nacos.svc.cluster.local:8848", "failAccessCnt": 0, "abilities": { "remoteAbility": { "supportRemoteConnection": true }, "configAbility": { "supportRemoteMetrics": false }, "namingAbility": { "supportJraft": true } } } ] }Desktop (please complete the following information):
提问
The cluster is running normally with no error logs.
Is this issue a defect in Nacos version 2.1.2, a chart version flaw, a deployment method problem, or have I missed any operational steps? How can we resolve this issue in a Kubernetes Nacos cluster? Any other suggestions would be appreciated.
Thanks for support .
集群运行正常,日志无报错。
该问题是nacos 2.1.2 版本缺陷、还是 chart 版本缺陷、还是部署方式的问题,或者是我遗漏了什么操作步骤?如何解决 k8s 中 nacos 集群的这个问题?以及其他建议。
谢谢。
All reactions