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]: Empty import task result #38313

Open
1 task done
bigsheeper opened this issue Dec 9, 2024 · 1 comment
Open
1 task done

[Bug]: Empty import task result #38313

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

Comments

@bigsheeper
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: master&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

When DataCoord fails to connect to DataNode due to an abnormality, the import task might be rescheduled. If the cluster has only one DataNode, the task will be assigned to the same DataNode. In this case, the old task on the DataNode will be replaced with the new task, resulting in an empty import result.
We should to ensure the idempotency of import tasks to prevent duplicate tasks in DataNode.

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response
@bigsheeper bigsheeper 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 Dec 9, 2024
@bigsheeper bigsheeper self-assigned this Dec 9, 2024
This was referenced Dec 9, 2024
Merged
Merged
@bigsheeper
Copy link
Contributor Author

image

@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 Dec 10, 2024
@bigsheeper bigsheeper mentioned this issue Dec 10, 2024
Merged
sre-ci-robot pushed a commit that referenced this issue Dec 11, 2024
@bigsheeper
fix: [2.4] Fix empty import task result (#38317)
9765db2 
Ensure the idempotency of import tasks to prevent duplicate tasks in
DataNode.

issue: #38313

pr: #38316

Signed-off-by: bigsheeper <[email protected]>
sre-ci-robot pushed a commit that referenced this issue Dec 11, 2024
@bigsheeper
fix: Fix empty import task result (#38316)
43e0e2b 
Ensure the idempotency of import tasks to prevent duplicate tasks in
DataNode.

issue: #38313

Signed-off-by: bigsheeper <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bigsheeper bigsheeper

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
@bigsheeper @yanliang567