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]: message=incomplete query result, missing id 455220550158615264 #39280

Open
1 task done
lingvisa opened this issue Jan 15, 2025 · 6 comments
Open
1 task done

[Bug]: message=incomplete query result, missing id 455220550158615264 #39280

lingvisa opened this issue Jan 15, 2025 · 6 comments
Assignees
Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@lingvisa
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Environment

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

Current Behavior

I have a query "SAP Cloud ALM", which works on one collection, dense, sparse and hybrid. But when I switched to another much bigger collection, sparse and dense still works, but hybrid failed with the following error message:

pymilvus.exceptions.MilvusException: <MilvusException: (code=2200, message=incomplete query result, missing id 455220550158615264, len(searchIDs) = 3, len(queryIDs) = 2, collection=455220550160477820: inconsistent requery result)>

Expected Behavior

No error message with corrct results

Steps To Reproduce

Milvus Log

No response

Anything else?

No response

@lingvisa lingvisa 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 Jan 15, 2025
@lingvisa
Copy link
Author

The search code is an adaptation of this one:

https://milvus.io/docs/full_text_search_with_milvus.md

@lingvisa
Copy link
Author

lingvisa commented Jan 15, 2025

There is an open similar one, but the way to use API is different, so I created one here. This is an real issue!

It may be helpful to create a larger collection and you might have a good chance to reproduce. My collection has only 23000 chunks and got this issue. I run the tutorial example and had no issue.

@yhmo
Copy link
Contributor

yhmo commented Jan 15, 2025

Link to this issue: #38831
Hopefully, it is fixed in v2.5.3, you can try upgrading to v2.5.3.

@yanliang567
Copy link
Contributor

@lingvisa please retry on Milvus v.2.5.3, and help to attach the milvus logs for investigation if it persisted.
/assign @yhmo
/unassign

@sre-ci-robot sre-ci-robot assigned yhmo and unassigned yanliang567 Jan 16, 2025
@yanliang567 yanliang567 added triage/needs-information Indicates an issue needs more information in order to work on it. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 16, 2025
@yanliang567 yanliang567 assigned lingvisa and unassigned yhmo Jan 16, 2025
@lingvisa
Copy link
Author

2.5.3 seems to fix the issue. I will update once new findings are found.

Copy link

stale bot commented Feb 15, 2025

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 Feb 15, 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 stale indicates no udpates for 30 days triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

3 participants