-
Notifications
You must be signed in to change notification settings - Fork 69
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
"Unknown MySQL server host" during "helm uninstall.." for starrocks #558
Comments
The first time encountering this error, can you provide the specific helm uninstall command you used? |
I can partially reproduce your error. The
However, the
|
Will try to fix it. |
Describe the bug
helm uninstall causes Segmentation fault. Following are the logs:
*** Aborted at 1715973973 (unix time) try "date -d @1715973973" if you are using GNU date ***
PC: @ 0x0 (unknown)
*** SIGSEGV (@0x0) received by PID 30 (TID 0x7fdf48b98640) from PID 0; stack trace: ***
@ 0x83d2d9a google::(anonymous namespace)::FailureSignalHandler()
@ 0x7fef4f499811 (unknown)
@ 0x7fef4f498e15 (unknown)
@ 0x7ff01e463520 (unknown)
@ 0x0 (unknown)
/opt/starrocks/cn_entrypoint.sh: line 185: 30 Segmentation fault $STARROCKS_HOME/bin/start_cn.sh $addition_args
[Fri May 17 19:26:13 UTC 2024] Receives signal to exit ...
[Fri May 17 19:26:13 UTC 2024] Can't find /opt/starrocks/cn/bin/cn.pid!
[Fri May 17 19:26:13 UTC 2024] try to drop myself(kube-starrocks-cn-0.kube-starrocks-cn-search.db-a72264f6b04249b.svc.cluster.local) from FE ...
ERROR 2005 (HY000): Unknown MySQL server host 'kube-starrocks-fe-service' (-3)
[Fri May 17 19:26:19 UTC 2024] Got error 1, sleep and retry ...
[Fri May 17 19:26:21 UTC 2024] try to drop myself(kube-starrocks-cn-0.kube-starrocks-cn-search.db-a72264f6b04249b.svc.cluster.local) from FE ...
ERROR 2005 (HY000): Unknown MySQL server host 'kube-starrocks-fe-service' (-3)
[Fri May 17 19:26:27 UTC 2024] Got error 1, sleep and retry ...
[Fri May 17 19:26:29 UTC 2024] try to drop myself(kube-starrocks-cn-0.kube-starrocks-cn-search.db-a72264f6b04249b.svc.cluster.local) from FE ...
It goes in the infinite loop and print above log in loop. This delays the whole deletion flow.
Kubernetes eventually kills the pod after it remains in this state for the maximum shutdown timeout.
Potential reason :
The order in which FE and CN services are deleted. FE gets deleted first and then CN.
Expected behavior
Helm uninstall should terminate all involved services smoothly with no Segmentation fault or infinite loop.
Please complete the following information
The text was updated successfully, but these errors were encountered: