-
Notifications
You must be signed in to change notification settings - Fork 14
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
helm布署的,模拟故障,删除所有pod后,无法自动恢复。 #39
Comments
这个问题请问解决了吗?感觉就像个半成品 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
版本
helm install tdengine3 -n xx-ns xx/tdengine --version 3.0.2
--create-namespace
--set replicaCount=3
--set storage.dataSize=100Gi
--set storage.logSize=2Gi
--values <(echo '
{"taoscfg":{"TAOS_REPLICA":"3","TAOS_NUM_OF_MNODES":"3"}}
')
04/23 12:11:21.138460 00000091 SYN ERROR failed to resolve ipv4 addr, fqdn: tdengine3-1.tdengine3.iot-ns.svc.cluster.local
04/23 12:11:21.138480 00000091 SYN ERROR vgId:3, failed to determine raft member id, peer:0
04/23 12:11:21.138493 00000091 SYN ERROR vgId:3, failed to open sync node
04/23 12:11:21.138558 00000091 VND ERROR vgId:3, failed to open sync since Invalid host name
04/23 12:11:21.138563 00000091 VND ERROR vgId:3, failed to open sync since Invalid host name
04/23 12:11:21.138671 00000090 SYN ERROR failed to resolve ipv4 addr, fqdn: tdengine3-1.tdengine3.iot-ns.svc.cluster.local
04/23 12:11:21.138682 00000090 SYN ERROR vgId:2, failed to determine raft member id, peer:0
04/23 12:11:21.138693 00000090 SYN ERROR vgId:2, failed to open sync node
04/23 12:11:21.138697 00000090 VND ERROR vgId:2, failed to open sync since Invalid host name
04/23 12:11:21.138701 00000090 VND ERROR vgId:2, failed to open sync since Invalid host name
04/23 12:11:21.139889 00000091 DND ERROR vgId:3, failed to open vnode by thread:1
04/23 12:11:21.139954 00000090 DND ERROR vgId:2, failed to open vnode by thread:0
04/23 12:11:21.140001 00000054 DND ERROR there are total vnodes:2, opened:0
04/23 12:11:21.140011 00000054 DND ERROR failed to open vnode since success
04/23 12:11:21.140014 00000054 DND ERROR failed to init vnodes-mgmt since success
04/23 12:11:21.140018 00000054 DND start to close all vnodes
04/23 12:11:21.140047 00000089 UTL worker:vnode-mgmt:0 qset:0x49fc5d0, got no message and exiting, thread:00000089
04/23 12:11:21.140089 00000054 DND vnodes mgmt worker is stopped
04/23 12:11:21.140102 00000054 DND close 0 vnodes with 8 threads
The text was updated successfully, but these errors were encountered: