-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[Bug][Cluster][Kubernetes]: All Milvus nodes and coordinators are stuck in CrashLoopBackOff #37459
Comments
missing source yaml @LoveEachDay could you help on investigating on this? |
meanwhile @SalBakraa could you verify which document you are actually following? did you put the right milvus config file |
/assign @LoveEachDay |
@SalBakraa Could you show us the |
I followed the step on https://milvus.io/docs/install_cluster-milvusoperator.md for installing milvus. For the milvus config I tried different configs. I tried the default cluster config, I also tried the one generate from the milvus sizing tool. The final config I settled on is a an edited version of the one generated by the milvus sizing tool.
|
@SalBakraa Could you log in to the worker node where the Milvus pod is running and check the CPU instructions using the following command?
|
Here are the flags on the host machine:
|
@LoveEachDay Thank you so much for the help. I only checked if the host CPU supported the instruction sets required by milvus; It didn't occur to me that VM CPU would be any different. Adding Now issue #34983 popped up and the querynode is crashing, but thankfully it looks like the fix is simple. Again, thank you so much for your help in debugging this issue. |
Is there an existing issue for this?
Environment
Current Behavior
Milvus Cluster fails to run on a Virtual Kubernetes Cluster. All milvus nodes and coordinators become stuck in CrashLoopBackOff state.
Expected Behavior
All milvus pods are Running and Ready.
Steps To Reproduce
setup_nfs_server.sh
:run_cluster.sh
:setup_cluster.sh
:operator-milvus-config.yaml
:install_milvus.sh
The text was updated successfully, but these errors were encountered: