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]: Query with large numbers of original vectors returned stuck when there is less disk space left, which will lead all the other search/query request hangs without no results #35184

Open
1 task done
binbinlv opened this issue Aug 1, 2024 · 1 comment
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

@binbinlv
Copy link
Contributor

binbinlv commented Aug 1, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

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

Current Behavior

Query with large numbers of original vectors returned stuck when there is less disk space left, which will lead all the other search/query request hangs without no results

Expected Behavior

Report error when the returned data is not able to return for milvus, and other search/query request should not be impacted

Steps To Reproduce

No response

Milvus Log

The log is on the zilliz cloud, please contact me if needed.

Anything else?

No response

@binbinlv binbinlv added kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Aug 1, 2024
@binbinlv binbinlv added this to the 2.4.7 milestone Aug 1, 2024
MrPresent-Han pushed a commit to MrPresent-Han/milvus that referenced this issue Aug 1, 2024
MrPresent-Han pushed a commit to MrPresent-Han/milvus that referenced this issue Aug 1, 2024
MrPresent-Han pushed a commit to MrPresent-Han/milvus that referenced this issue Aug 1, 2024
MrPresent-Han pushed a commit to MrPresent-Han/milvus that referenced this issue Aug 1, 2024
MrPresent-Han pushed a commit to MrPresent-Han/milvus that referenced this issue Aug 2, 2024
MrPresent-Han pushed a commit to MrPresent-Han/milvus that referenced this issue Aug 2, 2024
MrPresent-Han pushed a commit to MrPresent-Han/milvus that referenced this issue Aug 2, 2024
MrPresent-Han pushed a commit to MrPresent-Han/milvus that referenced this issue Aug 2, 2024
sre-ci-robot pushed a commit that referenced this issue Aug 2, 2024
…) (#35189)

related: #35184
pr: #35187

Signed-off-by: MrPresent-Han <[email protected]>
Co-authored-by: MrPresent-Han <[email protected]>
MrPresent-Han pushed a commit to MrPresent-Han/milvus that referenced this issue Aug 12, 2024
@yanliang567 yanliang567 modified the milestones: 2.4.7, 2.4.8 Aug 12, 2024
MrPresent-Han pushed a commit to MrPresent-Han/milvus that referenced this issue Aug 16, 2024
MrPresent-Han pushed a commit to MrPresent-Han/milvus that referenced this issue Aug 19, 2024
@yanliang567 yanliang567 modified the milestones: 2.4.8, 2.4.10 Aug 19, 2024
sre-ci-robot pushed a commit that referenced this issue Aug 19, 2024
…) (#35187)

related: #35184

Signed-off-by: MrPresent-Han <[email protected]>
Co-authored-by: MrPresent-Han <[email protected]>
@yanliang567 yanliang567 modified the milestones: 2.4.10, 2.4.11 Sep 5, 2024
@yanliang567 yanliang567 modified the milestones: 2.4.11, 2.4.12 Sep 18, 2024
@yanliang567 yanliang567 modified the milestones: 2.4.12, 2.4.13 Sep 27, 2024
@MrPresent-Han
Copy link
Contributor

/assign binbinlv

@yanliang567 yanliang567 modified the milestones: 2.4.13, 2.4.14 Oct 15, 2024
@yanliang567 yanliang567 modified the milestones: 2.4.14, 2.4.16 Nov 14, 2024
@yanliang567 yanliang567 modified the milestones: 2.4.16, 2.4.17, 2.4.18 Nov 21, 2024
@yanliang567 yanliang567 modified the milestones: 2.4.18, 2.4.19, 2.4.20 Dec 24, 2024
@yanliang567 yanliang567 modified the milestones: 2.4.20, 2.4.21 Jan 6, 2025
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

3 participants