-
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]: After mixcoord rolling upgrade, a restart occurs, and then it remains in an unhealthy state and cannot be recovered #37432
Labels
kind/bug
Issues or changes related a bug
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
severity/critical
Critical, lead to crash, data missing, wrong result, function totally doesn't work.
test/rolling upgrade
Comments
zhuwenxing
added
kind/bug
Issues or changes related a bug
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
Nov 5, 2024
zhuwenxing
added
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
severity/critical
Critical, lead to crash, data missing, wrong result, function totally doesn't work.
labels
Nov 5, 2024
/assign @weiliu1031 |
when deploy mode is cluster, the datacoord is keeping crash during upgrade
|
known issue, should be fixed by #37418, please verify this with latest image |
/assign @zhuwenxing |
verified and fixed in master-20241105-b83b376c-amd64 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/bug
Issues or changes related a bug
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
severity/critical
Critical, lead to crash, data missing, wrong result, function totally doesn't work.
test/rolling upgrade
Is there an existing issue for this?
Environment
Current Behavior
mixcoord rolling update finished
mixcoord restarted
after 4min,mixcoord still in unhealthy status
Expected Behavior
No response
Steps To Reproduce
No response
Milvus Log
failed job: https://qa-jenkins.milvus.io/blue/organizations/jenkins/rolling_update_for_operator_test_simple/detail/rolling_update_for_operator_test_simple/5441/pipeline/82/
log:
artifacts-kafka-mixcoord-5441-server-logs.tar.gz
Anything else?
No response
The text was updated successfully, but these errors were encountered: