当读取CPU资源指标有问题时，自动缩放机制将扩展为最少的实例数 [英] Autoscale mechanism scales in to minimum instance count when there is a problem reading CPU resource metrics

问题描述

在2008年4月9日各种Azure服务中断期间，这些服务似乎使美国中部地区的云服务无法使用CPU资源指标，因此Autoscale会扩展到我们的最小实例数，而不是我们的默认实例数.这里是 门户中默认实例计数字段上的工具提示文档:

During the 09/04/18 outage of various Azure services that seemed to make CPU resources metrics unavailable for cloud services in the Central US region, Autoscale scaled in to our minimum instance count rather than our default instance count. Here is the tooltip documentation on the default instance count field in the portal:

如果读取资源度量标准时出现问题，并且当前容量低于默认容量，则为确保资源的可用性，Autoscale将横向扩展到默认值.如果当前容量已经高于 默认容量，自动缩放"将不会放大.

In case there is a problem reading the resource metrics and the current capacity is below the default capacity, then to ensure the availability of the resource, Autoscale will scale out to the default. If the current capacity is already higher than the default capacity, Autoscale will not scale in.

在此中断期间，自动缩放功能似乎无法正常运行?

Autoscale didn't seem to work as documented during this outage?

推荐答案

在9/4上，还有其他一些区域有问题.曾经是美国中部.

On 9/4 there were some other regions that had issues. Once of which was Central US. 

问题涉及存储，这也会影响自动扩展.

The issues were surrounding storage which would also impact auto scaling. 

您可以监视"Azure状态"页面以获取根本原因的更新.

You can monitor the Azure Status page for updates on the full root cause. 

https://azure.microsoft.com/en-us/status/

您的服务现在恢复正常了吗?

Is your service back to normal now? 

这篇关于当读取CPU资源指标有问题时，自动缩放机制将扩展为最少的实例数的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！