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.

Sign up for GitHub

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

Jump to bottom

[Bug]: concurrent delete might cause mvcc timestamp failed to work #38961

Closed
1 task done
congqixia opened this issue Jan 2, 2025 · 0 comments
Closed
1 task done

[Bug]: concurrent delete might cause mvcc timestamp failed to work #38961

congqixia opened this issue Jan 2, 2025 · 0 comments
Assignees
@congqixia
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@congqixia
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Environment

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

Current Behavior

when lower_bound CSL of result is end(), concurrent delete records could break mvcc timestamp logic causing inconsistent query result error

Expected Behavior

delete record shall work find under concurrent read & delete

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response
@congqixia congqixia added kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Jan 2, 2025
@congqixia congqixia self-assigned this Jan 2, 2025
congqixia added a commit to congqixia/milvus that referenced this issue Jan 2, 2025
@congqixia
fix: Check query_timestamp in case of concurrent delete
7344758 
Related to milvus-io#38961

Signed-off-by: Congqi Xia <[email protected]>
congqixia added a commit to congqixia/milvus that referenced this issue Jan 2, 2025
@congqixia
fix: Check query_timestamp in case of concurrent delete
96129ee 
Related to milvus-io#38961

Signed-off-by: Congqi Xia <[email protected]>
@congqixia congqixia mentioned this issue Jan 2, 2025
Closed
@zhagnlu zhagnlu mentioned this issue Jan 3, 2025
Merged
sre-ci-robot pushed a commit that referenced this issue Jan 6, 2025
@zhagnlu
fix: fix query incorrect in case of concurrent delete (#38991)
8165044 
#38961

Signed-off-by: luzhang <[email protected]>
Co-authored-by: luzhang <[email protected]>
zhagnlu added a commit to zhagnlu/milvus that referenced this issue Jan 7, 2025
@zhagnlu
fix: fix query incorrect in case of concurrent delete (milvus-io#38991)
6750b97 
milvus-io#38961

Signed-off-by: luzhang <[email protected]>
Co-authored-by: luzhang <[email protected]>
@zhagnlu zhagnlu mentioned this issue Jan 7, 2025
Merged
@xiaofan-luan xiaofan-luan mentioned this issue Jan 7, 2025
Open
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@congqixia congqixia

Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@congqixia