Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[Bug]: Milvus crashes when running go-sdk e2e case when trying to load a collection #39704

Closed
1 task done
yanliang567 opened this issue Feb 8, 2025 · 7 comments
Closed
1 task done
Assignees
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@yanliang567
Copy link
Contributor

yanliang567 commented Feb 8, 2025

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version:
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

Milvus crashes

Image

Expected Behavior

no crash

Steps To Reproduce

go sdk test in pr
https://jenkins.milvus.io:18080/blue/organizations/jenkins/Milvus%20HA%20CI(go-sdk)/detail/PR-39691/2/pipeline

Milvus Log

https://grafana-4am.zilliz.cc/explore?panes=%7B%22EoD%22:%7B%22datasource%22:%22vhI6Vw67k%22,%22queries%22:%5B%7B%22refId%22:%22A%22,%22expr%22:%22%7Bpod%3D%5C%22ms-39691-2-go-pr-milvus-standalone-5c57766fdd-8d86w%5C%22%7D%20%7C~%20%5C%22%5C%22%22,%22queryType%22:%22range%22,%22datasource%22:%7B%22type%22:%22loki%22,%22uid%22:%22vhI6Vw67k%22%7D,%22editorMode%22:%22code%22%7D%5D,%22range%22:%7B%22from%22:%221738984531000%22,%22to%22:%221738984658000%22%7D%7D%7D&schemaVersion=1&orgId=1

No response

Anything else?

No response

@yanliang567 yanliang567 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 Feb 8, 2025
@yanliang567 yanliang567 self-assigned this Feb 8, 2025
@yanliang567
Copy link
Contributor Author

/assign @xiaocai2333
/unassign

@yanliang567 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 Feb 8, 2025
@xiaofan-luan
Copy link
Collaborator

@yanliang567
already a fixed issue of 2.5.4

@xiaofan-luan
Copy link
Collaborator

tantivy related issue

@yanliang567
Copy link
Contributor Author

But this is on the master branch, and I just rebased this morning.

@yanliang567
Copy link
Contributor Author

/assign @xiaocai2333
please help to double confirm

@xiaocai2333
Copy link
Contributor

fix by #39253
/assign @sunby

@yanliang567
Copy link
Contributor Author

dup to #39585

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

4 participants