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]: SyncSegments rpc always failed #38031

Closed
1 task done
weiliu1031 opened this issue Nov 26, 2024 · 1 comment
Closed
1 task done

[Bug]: SyncSegments rpc always failed #38031

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

Comments

@weiliu1031
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: 2.4
- 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

cause call cli.SyncSegments use ctx which already be override and canceled, so SyncSegments rpc will always failed.

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response
@weiliu1031 weiliu1031 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 Nov 26, 2024
@weiliu1031 weiliu1031 mentioned this issue Nov 26, 2024
Merged
@weiliu1031
Copy link
Contributor Author

/assign

@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 Nov 26, 2024
@yanliang567 yanliang567 removed their assignment Nov 26, 2024
sre-ci-robot pushed a commit that referenced this issue Nov 28, 2024
@weiliu1031
fix: SyncSegments rpc always failed (#38032)
88b731d 
issue: #38031
cause call `cli.SyncSegments` use ctx which already be override and
canceled, so SyncSegments rpc will always failed.

Signed-off-by: Wei Liu <[email protected]>
congqixia pushed a commit to congqixia/milvus that referenced this issue Dec 19, 2024
@weiliu1031 @congqixia
fix: SyncSegments rpc always failed (milvus-io#38032)
8066726 
issue: milvus-io#38031
cause call `cli.SyncSegments` use ctx which already be override and
canceled, so SyncSegments rpc will always failed.

Signed-off-by: Wei Liu <[email protected]>
Signed-off-by: Congqi Xia <[email protected]>
@congqixia congqixia mentioned this issue Dec 19, 2024
Merged
czs007 pushed a commit that referenced this issue Dec 19, 2024
@congqixia @weiliu1031
fix: [10kcp] SyncSegments rpc always failed (#38032) (#38579)
f5ae24f 
Cherry-pick from 2.4
pr: #38032
issue: #38031
cause call `cli.SyncSegments` use ctx which already be override and
canceled, so SyncSegments rpc will always failed.

Signed-off-by: Wei Liu <[email protected]>
Signed-off-by: Congqi Xia <[email protected]>
Co-authored-by: wei liu <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@weiliu1031 weiliu1031

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
2 participants
@yanliang567 @weiliu1031