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]: deletion problem #35491

Closed
1 task done
zs856 opened this issue Aug 15, 2024 · 3 comments
Closed
1 task done

[Bug]: deletion problem #35491

zs856 opened this issue Aug 15, 2024 · 3 comments
Assignees
Labels
help wanted Extra attention is needed stale indicates no udpates for 30 days

Comments

@zs856
Copy link

zs856 commented Aug 15, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

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

Current Behavior

Today, while I was following the official documentation to practice the deletion operation, I found that the data was not successfully deleted. You can check the uploaded .ipynb file to see the code I ran. The development environment can also be reproduced using pyproject.toml and Docker Compose.

milvus-deletion-bug.zip

Expected Behavior

I expect the data in the Collection to be successfully deleted as it is executed in the code of the official documentation.

Steps To Reproduce

1. Deploy milvus using the docker compose file I provided
2. Set up development environment using the pyproject (1).toml I provided
3. Run the code inside 删除bug.ipynb

Milvus Log

No response

Anything else?

No response

@zs856 zs856 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 15, 2024
@XuanYang-cn
Copy link
Contributor

XuanYang-cn commented Aug 15, 2024

@zs856 Hi, thx for the detailed bug report and reproducable codes.
I noticed that you're usingclient.get_collection_stats(collection_name='quick_setup') to verify correcteness of deletion. Accually get_collection_stats are neither realtime nor accurate, espcially for deletions.

Please try to use query(count(*)), or query() those deleted pks with strong consistency level. See https://milvus.io/docs/get-and-scalar-query.md#Use-Advanced-Operators

client.query(...., output_fields=["count(*)"], consistency_level="Strong")

@yanliang567
Copy link
Contributor

/assign @zs856
/unassign

@sre-ci-robot sre-ci-robot assigned zs856 and unassigned yanliang567 Aug 16, 2024
@yanliang567 yanliang567 added help wanted Extra attention is needed and removed 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 16, 2024
Copy link

stale bot commented Sep 20, 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 Sep 20, 2024
@stale stale bot closed this as completed Nov 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed stale indicates no udpates for 30 days
Projects
None yet
Development

No branches or pull requests

3 participants