-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
CQ: Queue crash using SAC #5460
Comments
Any news related to this topic? |
I had a quick look and indeed could reproduce easily using the provided Go code, but somehow not using perf-test. Anyway, the stacktrace is:
Seems like the backing queue is not empty in this case: I'll defer to @lhoguin as it also affects CQv2. |
Hello, we will take a look next week. In the meantime it would be helpful if you could check whether the problem also occurs on 3.9. |
Hello. @lhoguin Thanks for taking a look soon. |
Alright thanks that helps a lot, it means the problem is not related to the many changes I have done since 3.10. I'll get back to you when I have something. |
Hello, I have pushed a potential fix in the following PR: #6502 Culprit was an old assertion that I do not believe is necessary, but tests haven't finished running, so we will see. |
PR was merged so I'm closing this issue. Thanks! |
From this issue rabbitmq/amqp091-go#106, we found a reliable way to reproduce a queue crash using 2 consumers in a Single Active Consumer enabled Classic Queue.
I will upload a slight modified version of the original code to reproduce the issue in rabbitmq/amqp091-go#106 to a gist shortly.Code for repro: https://github.com/Zerpet/amqp091-go-repro-106/tree/main
Steps to repro:
Observed behaviour:
The issue referenced has RabbitMQ logs attached with the error mentioned above.
The text was updated successfully, but these errors were encountered: