We were experiencing performance issues when we migrated a message queuing node to our new network. This affected clients consuming from partitions on that node, particularly Document Translation services. The slowdown occurred because the message queue had to replicate partitions to the rejoined node-a resource-intensive process given our data volume.
We've since implemented improvements, including scheduling migrations during off-peak hours and improving replication monitoring. We apologize for the disruption and are committed to preventing similar incidents.