<div dir="ltr">RabbitMQ team ... would you mind posting the internal bug reports for the following Bug IDs since you don't have a public bug tracker? We're digging into some failures we had today, and trying to understand which one of these (if any) bugs may have bit us:<div>
<br></div><div><div>25615 25670 fix race conditions in mirrored queues when different cluster</div><div> nodes start and stop near-simultaneously (since 2.6.0)</div><div>25617 fix corrupt_cluster_status_files error after abrupt node shutdown</div>
<div> (since 3.0.0)</div><div><div>25632 fix broken error handling in amqp_network_connection that could lead</div><div> to a crash during broker shutdown (since 2.4.0)</div></div><div>25602 fix race condition that could cause mirrored queues to corrupt state<br>
</div><div><div> during promotion (since 2.6.0)</div></div><div><div>25745 prevent HA queue from becoming masterless if multiple nodes shutdown in</div><div> quick succession (since 2.6.0)</div><div>25685 prevent race that leads to a masterless queue when a slave and</div>
<div> previous master start simultaneously (since 2.6.0)</div></div><div><br></div>
</div></div>