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]: Graceful stop datanode gets stuck #34736

Closed
1 task done
bigsheeper opened this issue Jul 16, 2024 · 1 comment
Closed
1 task done

[Bug]: Graceful stop datanode gets stuck #34736

bigsheeper opened this issue Jul 16, 2024 · 1 comment
Assignees
@bigsheeper
Labels
kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. stale indicates no udpates for 30 days

Comments

@bigsheeper
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Environment

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

Even though the compaction task was completed a long time ago, closing flushManager still gets stuck. Analyzing the logs, I found that the injectDone function was never called for this compaction task, causing flushManager to hang and not exit.

image

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 Jul 16, 2024
@bigsheeper bigsheeper self-assigned this Jul 16, 2024
@bigsheeper bigsheeper mentioned this issue Jul 16, 2024
Merged
sre-ci-robot pushed a commit that referenced this issue Jul 17, 2024
@bigsheeper
fix: Discard compaction plan when closing dataSyncService (#34737)
3d9ec2a 
issue: #34736

---------

Signed-off-by: bigsheeper <yihao.dai@zilliz.com>
@stale Stale
Copy link

stale bot commented Aug 18, 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 Aug 18, 2024
@stale stale bot closed this as completed Aug 31, 2024
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 needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. stale indicates no udpates for 30 days
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bigsheeper