Whole RabbitMQ startup stuck if recovering one queue index crashes #8325
-
I am reproducing this on main @ 7e3fa92 but we've seen this on 3.11.x in the wild. When persistent message store is recovering it goes through the files of classic queue indices. I intentionally corrupted one queue data so it crashes. What is initially unexpected to me is that the startup of RabbitMQ is blocked and never finishes. As it is stuck in the rabbit app startup the plugins like the management plugin are never started, so it's not fully visible what the status is. I got as far in tracking down the issue that the persistent msg store process is waiting for the results via a Log snippets
Process infos
This needs no mirroring and can affect CQv2 as well (if we are able to crash Is there anything that could be done about this? What is the background of commit ad20a63? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
I have opened #8338 to revert the commit as it doesn't seem necessary anymore. It seemed necessary while developing CQv2 initially but I guess it was a mistake. |
Beta Was this translation helpful? Give feedback.
I have opened #8338 to revert the commit as it doesn't seem necessary anymore. It seemed necessary while developing CQv2 initially but I guess it was a mistake.