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.

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

[Bug]: Rocksmq may cause deadlock when close consumer in ut. #39336

Open
1 task done
aoiasd opened this issue Jan 16, 2025 · 2 comments
Open
1 task done

[Bug]: Rocksmq may cause deadlock when close consumer in ut. #39336

aoiasd opened this issue Jan 16, 2025 · 2 comments
Assignees
Labels
kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@aoiasd
Copy link
Contributor

aoiasd commented Jan 16, 2025

Is there an existing issue for this?

  • I have searched the existing issues

Environment

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

https://github.com/milvus-io/milvus/actions/runs/12763634683/job/35577210669?pr=38656
Consumer's goroutine cannot consume from

Expected Behavior

No response

Steps To Reproduce

Milvus Log

No response

Anything else?

No response

@aoiasd aoiasd 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 Jan 16, 2025
@aoiasd
Copy link
Contributor Author

aoiasd commented Jan 16, 2025

/unassign @yanliang567
/assign @aoiasd

@sre-ci-robot sre-ci-robot assigned aoiasd and unassigned yanliang567 Jan 16, 2025
@aoiasd
Copy link
Contributor Author

aoiasd commented Jan 16, 2025

Find rocksmq consumer map not concurrent safe, will fix later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants