-
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]: search failed with error segment lacks[segment=451679606836035900]: channel not available
after standalone pod kill chaos test
#35361
Labels
kind/bug
Issues or changes related a bug
test/chaos
chaos test
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Milestone
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
Aug 8, 2024
/assign @weiliu1031 |
not a stable reproduced issue |
This was referenced Aug 8, 2024
yanliang567
added
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
and removed
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
Aug 8, 2024
sre-ci-robot
pushed a commit
that referenced
this issue
Aug 13, 2024
sre-ci-robot
pushed a commit
that referenced
this issue
Aug 15, 2024
issue: #35361 Signed-off-by: Wei Liu <wei.liu@zilliz.com>
please verify this with latest image |
/assign @zhuwenxing |
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
test/chaos
chaos test
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Is there an existing issue for this?
Environment
Current Behavior
Expected Behavior
No response
Steps To Reproduce
No response
Milvus Log
failed job: https://qa-jenkins.milvus.io/blue/organizations/jenkins/chaos-test-kafka-for-release-cron/detail/chaos-test-kafka-for-release-cron/15665/pipeline
log:
artifacts-standalone-pod-kill-15665-server-logs.tar.gz
cluster: 4am
ns:chaos-testing
pod
Anything else?
No response
The text was updated successfully, but these errors were encountered: