Reitse Eskens runs into a strange bug in Azure SQL Database Hyperscale:
This single wait made sure our complete environment went dead in the water. Everything halted. To get some context, Microsoft has some documentation on this wait:
Occurs when a Hyperscale database primary compute node log generation rate is being throttled due to delayed log consumption at the page server(s).
Well, that’s not really helping, because that’s about everything they tell you about it.
Click through for Reitse’s findings and Microsoft’s advice.