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]: Delete of SealedSegment may lost when enable lazy load. #31794

Open
1 task done
chyezh opened this issue Apr 1, 2024 · 3 comments
Open
1 task done

[Bug]: Delete of SealedSegment may lost when enable lazy load. #31794

chyezh opened this issue Apr 1, 2024 · 3 comments
Assignees
@chyezh
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@chyezh
Copy link
Contributor

chyezh commented Apr 1, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

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

Current Behavior

Delete of SealedSegment may lost when enable lazy load

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response
@chyezh chyezh 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 Apr 1, 2024
@chyezh chyezh mentioned this issue Apr 1, 2024
Closed
@yanliang567
Copy link
Contributor

/assign @chyezh
/unassign

@sre-ci-robot sre-ci-robot assigned chyezh and unassigned yanliang567 Apr 1, 2024
@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 Apr 1, 2024
@chyezh chyezh mentioned this issue Apr 15, 2024
Merged
@stale Stale
Copy link

stale bot commented May 1, 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 May 1, 2024
@xiaofan-luan
Copy link
Contributor

keep it as an issue

@stale stale bot removed the stale indicates no udpates for 30 days label May 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chyezh chyezh

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
3 participants
@chyezh @yanliang567 @xiaofan-luan