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]: Reduce didn't stop when draining one result source #36179

Open
1 task done
MrPresent-Han opened this issue Sep 11, 2024 · 2 comments
Open
1 task done

[Bug]: Reduce didn't stop when draining one result source #36179

MrPresent-Han opened this issue Sep 11, 2024 · 2 comments
Assignees
Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@MrPresent-Han
Copy link
Contributor

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

Currently, when doing query iteration over a collection without setting reduce_stop_for_best=true, the step length of iterator may increase very fast unexpectedly, resulting in some data invisible to users.

Expected Behavior

Query Iterator can return all results as expected under various cases including insert/upsert/delete scenarios.

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

@MrPresent-Han MrPresent-Han 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 Sep 11, 2024
MrPresent-Han pushed a commit to MrPresent-Han/milvus that referenced this issue Sep 11, 2024
Signed-off-by: MrPresent-Han <chun.han@gmail.com>
MrPresent-Han pushed a commit to MrPresent-Han/milvus that referenced this issue Sep 11, 2024
Signed-off-by: MrPresent-Han <chun.han@gmail.com>
MrPresent-Han pushed a commit to MrPresent-Han/milvus that referenced this issue Sep 11, 2024
Signed-off-by: MrPresent-Han <chun.han@gmail.com>
@yanliang567
Copy link
Contributor

/assign @MrPresent-Han
/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 Sep 12, 2024
MrPresent-Han pushed a commit to MrPresent-Han/milvus that referenced this issue Sep 14, 2024
Signed-off-by: MrPresent-Han <chun.han@gmail.com>
MrPresent-Han pushed a commit to MrPresent-Han/milvus that referenced this issue Sep 18, 2024
Signed-off-by: MrPresent-Han <chun.han@gmail.com>
sre-ci-robot pushed a commit that referenced this issue Sep 24, 2024
related: #36179

Signed-off-by: MrPresent-Han <chun.han@gmail.com>
Co-authored-by: MrPresent-Han <chun.han@gmail.com>
Copy link

stale bot commented Nov 9, 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 Nov 9, 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 stale indicates no udpates for 30 days triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

2 participants