Skip to content
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]: In the scenario of continuously inserting data and searching, milvus standalone will restart intermittently #37644

Open
1 task done
cqy123456 opened this issue Nov 13, 2024 · 4 comments
Assignees
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone

Comments

@cqy123456
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: v2.4.14-nightly-cedc3405-1293
- Deployment mode(standalone or cluster): standalone
- CPU/Memory: 8cu, 16c32g
- InstanceId:gcp, in01-f0530ceba1dd67f
- Others: 
Milvus config
dataCoord.segment.maxSize = 3G
dataCoord.segment.sealProportion = 0.04

Current Behavior

DataSet: corhere-768d-cosine
When insert rate at 4k/s:
image
image
When insert rate at 1k/s:
image
image

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

There is no stack when crashing.
image
image

Anything else?

No response

@cqy123456 cqy123456 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 13, 2024
@czs007 czs007 added this to the 2.5.0 milestone Nov 13, 2024
@czs007 czs007 self-assigned this Nov 13, 2024
@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 Nov 13, 2024
@yanliang567 yanliang567 removed their assignment Nov 13, 2024
@czs007
Copy link
Collaborator

czs007 commented Nov 13, 2024

trying to get the coredump file.

@liliu-z
Copy link
Member

liliu-z commented Nov 15, 2024

/assign @foxspy
Looks like from Cardinal

@cqy123456
Copy link
Contributor Author

/assign @hhy3

Copy link

stale bot commented Dec 21, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.

@stale stale bot added the stale indicates no udpates for 30 days label Dec 21, 2024
@yanliang567 yanliang567 modified the milestones: 2.5.0, 2.5.1 Dec 24, 2024
@stale stale bot removed the stale indicates no udpates for 30 days label Dec 24, 2024
@yanliang567 yanliang567 modified the milestones: 2.5.1, 2.5.2 Dec 30, 2024
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 triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

6 participants