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 failed because of wrong distribution on delegator #33089

Closed
1 task done
sunby opened this issue May 16, 2024 · 1 comment
Closed
1 task done

[Bug]: delete failed because of wrong distribution on delegator #33089

sunby opened this issue May 16, 2024 · 1 comment
Assignees
@sunby
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone
2.3.16

Comments

@sunby
Copy link
Contributor

sunby commented May 16, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: v2.3.15
- 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

concurrent sync and segment task may cause inconsistent distribution state on delegator.
the consequence of this problem is:
1.balance segment to a querynode and release segment on delegator.
2.sync may set this segment on delegator again.
3.query on this segment will be sent to delegator where the segment is already relased. And query will fail on this delegator.

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response
@sunby sunby 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 May 16, 2024
@sunby sunby mentioned this issue May 16, 2024
Merged
@yanliang567
Copy link
Contributor

/assign @sunby
/unassign

@sre-ci-robot sre-ci-robot assigned sunby and unassigned yanliang567 May 16, 2024
@yanliang567 yanliang567 added this to the 2.3.16 milestone May 16, 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 May 16, 2024
sre-ci-robot pushed a commit that referenced this issue May 17, 2024
@sunby
fix: avoid concurrent sync and segment tasks (#33087)
bbf3a27 
issue: #33089

---------

Signed-off-by: sunby <sunbingyi1992@gmail.com>
@sunby sunby closed this as completed May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sunby sunby

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
2.3.16
Development

No branches or pull requests
2 participants
@sunby @yanliang567