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

Clients stop consuming/producing after a follower is stopped when cluster is under high load #926

Open
spuun opened this issue Jan 30, 2025 · 1 comment · May be fixed by #927
Open

Clients stop consuming/producing after a follower is stopped when cluster is under high load #926

spuun opened this issue Jan 30, 2025 · 1 comment · May be fixed by #927
Assignees
@spuun
Labels
bug

Comments

@spuun
Copy link
Member

spuun commented Jan 30, 2025

Describe the bug
Clients can't publish or consume after a follower has been stopped.

Describe your setup
Tested on a CloudAMQP 3-node cluster with lavinmq 2.1

How to reproduce
Run lavinmqperf throughput against a cluster with followers. Stop one of the followers. Notice how throughput gets down to 0. It doesn't happen all the time so a few attempts may be needed.

Expected behavior
The cluster should continue to operate.
@spuun spuun added the bug label Jan 30, 2025
@spuun
Copy link
Member Author

spuun commented Jan 30, 2025

I'm pretty sure it's a deadlock related to the lock in Clustering::Server.

@spuun spuun self-assigned this Jan 30, 2025
@spuun spuun linked a pull request Jan 30, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@spuun spuun

Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Bugfix: deadlock when stopping follower cloudamqp/lavinmq
1 participant
@spuun