From @joec7B6 via Twitter,
For 75D, everything’s been stable with SBus until last Thursday when we started getting MessagingCommunicationException causing restarts to resolve. What up?
FYI, In March, we opened a support ticket and received this explanation for the outage:
Cause: Service Bus billing component was experiencing throttling errors while writing to permanent Azure storage. Some code paths are not handling these exceptions appropriately and resulting in internal server exceptions to our customers. In a couple of code paths it has blocked a node from coming up entirely and some role instances recycled a few times. This was causing client side out timeout errors.
Is there any way to be informed when our instances are impacted by events like these? Has anything like this been occurring over the past few days?
Thanks,
@AzureSupport
For 75D, everything’s been stable with SBus until last Thursday when we started getting MessagingCommunicationException causing restarts to resolve. What up?
FYI, In March, we opened a support ticket and received this explanation for the outage:
Cause: Service Bus billing component was experiencing throttling errors while writing to permanent Azure storage. Some code paths are not handling these exceptions appropriately and resulting in internal server exceptions to our customers. In a couple of code paths it has blocked a node from coming up entirely and some role instances recycled a few times. This was causing client side out timeout errors.
Is there any way to be informed when our instances are impacted by events like these? Has anything like this been occurring over the past few days?
Thanks,
@AzureSupport