milvus icon indicating copy to clipboard operation
milvus copied to clipboard

[Bug]: Insert 1m data to a collection but 1.01m data exists due to context cancel

Open NicoYuan1986 opened this issue 10 months ago • 2 comments

Is there an existing issue for this?

  • [X] I have searched the existing issues

Environment

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

Current Behavior

Insert 1m data to a collection but 1.01m data exists due to context cancel. image

Obviously, the different insert costs more time than another. Though there is not an error, the server does receive an error. img_v3_029v_0dfdb012-83bb-4471-95f9-f9f5f14dc44g

Because python sdk has retries and context done cannot cancel the task after insert task is queuing. This is an known issue.

Expected Behavior

no repeat insert

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

NicoYuan1986 avatar Apr 15 '24 08:04 NicoYuan1986

argo link: https://argo-workflows.cloud-uat.zilliz.cn/workflows/qa/platform-fouramf-bzmc9?tab=workflow&nodeId=platform-fouramf-bzmc9-797180194&sidePanel=logs:platform-fouramf-bzmc9-797180194:main case name: test_scene_go_bench_auto_index dataset: 768d-1m-gist

NicoYuan1986 avatar Apr 15 '24 12:04 NicoYuan1986

/assign @czs007 /unassign

yanliang567 avatar Apr 16 '24 01:04 yanliang567

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[bot] avatar Jun 16 '24 04:06 stale[bot]