-
Notifications
You must be signed in to change notification settings - Fork 33
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
unexpected: first deployment is not for group 0 #179
Comments
Starting from version 0.9.4, milvus-operator will create two deployments for querynode for high-availability rolling upgrades, querynode-0 and querynode-1. Now this error means that one of the deployments does not exist. If it is deleted by mistake, it needs to be restored. |
Thanks~ 🙏 |
OK,I "copy" querynode-1 deployment, and start a new deployment named "querynode-0". |
more info:
|
Thanks~ |
For some unknown reason, when upgrading Milvus from version 2.3.x to 2.4.6, the original query-0 pod became 0/0, similar to the standalone deployment.
Today, when upgrading the operator to version v1.0.3, I encountered the above error, but there were no issues when rolling back to version v0.9.14.
admin please fix this by setting a last deployment for group 0
How to do this?The text was updated successfully, but these errors were encountered: