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]: PartitionNotFound if the partition was new created and never be flushed #26113

Closed
1 task done
sunmingqiaa opened this issue Aug 3, 2023 · 4 comments
Closed
1 task done
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.
Milestone

Comments

@sunmingqiaa
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Environment

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

Current Behavior

Reproduction Process:

Create a table named "test" with two partitions, labeled as 1 and 2.
Insert a record into each partition, one in partition 1 and another in partition 2.
Perform searches on both partitions 1 and 2, which should return the respective records successfully.
Next, create a new partition labeled as 3 and insert a record into it. When attempting to search specifically in partition 3, the result shows "reason=stream operation failed: PartitionNotFound(partitionID=443277368143647844)".
After performing a flush operation, searches on partition 3 return the record normally.
After conducting multiple tests, it was observed that when creating one or two partitions initially and following steps 1, 2, and 3, searches work correctly. However, when executing step 4, an exception is encountered.

Expected Behavior

it should normal return result

Steps To Reproduce

Reproduction Process:

Create a table named "test" with two partitions, labeled as 1 and 2.
Insert a record into each partition, one in partition 1 and another in partition 2.
Perform searches on both partitions 1 and 2, which should return the respective records successfully.
Next, create a new partition labeled as 3 and insert a record into it. When attempting to search specifically in partition 3, the result shows "reason=stream operation failed: PartitionNotFound(partitionID=443277368143647844)".
After performing a flush operation, searches on partition 3 return the record normally.
After conducting multiple tests, it was observed that when creating one or two partitions initially and following steps 1, 2, and 3, searches work correctly. However, when executing step 4, an exception is encountered.

Milvus Log

Failed to search vectors in Milvus: <MilvusException: (code=1, message=fail to search on all shard leaders, err=All attempts results:\nattempt #1:code: UnexpectedError, error: fail to Search, QueryNode ID=6, reason=stream operation failed: PartitionNotFound(partitionID=443277368143647844)\nattempt #2:context canceled\n)

Anything else?

No response

@sunmingqiaa sunmingqiaa 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 Aug 3, 2023
@yanliang567
Copy link
Contributor

@jiaoew1991 sound like a corner issue that milvus did not sync the meta at once as partition created.
/assign @jiaoew1991
/unassign

@yanliang567 yanliang567 added this to the 2.3 milestone Aug 3, 2023
@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 Aug 3, 2023
@yanliang567
Copy link
Contributor

/assign @NicoYuan1986
can we add a new test for this

@yanliang567 yanliang567 changed the title [Bug]: PartitionNotFound [Bug]: PartitionNotFound if the partition was new created and never be flushed Aug 4, 2023
@xiaofan-luan
Copy link
Contributor

we are not support create partition while collection is loaded.
this is as expected in 2.2.12, we only load partitions list on the load

@stale
Copy link

stale bot commented Sep 3, 2023

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 Sep 3, 2023
@stale stale bot closed this as completed Sep 11, 2023
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

5 participants