为什么在Azure门户中不使用自动缩放功能来服务于织物缩放?

时间:2018-09-20 04:33:15

标签: azure-service-fabric autoscaling

我对服务矩阵群集进行了以下设置:

  1. 5个节点(耐用性等级:铜牌和可靠性等级:银牌)
  2. 相关VM规模集(VMSS)上的当前平均CPU利用率百分比平均值约为14%。
  3. 已正确部署每个服务,实例计数为-1。
  4. 我们使用上述服务的应用程序运行正常。

我使用azure门户尝试为上述VMSS设置自动缩放选项(在“缩放”选项中):

  1. 使用横向扩展,CPU利用率%的阈值为10(从上面开始,当前值为14)。
  2. 将其配置为等待5分钟后再放大。
  3. 其余细节显示在json下面。

{ "location": "eastus", "tags": { "$type": "Microsoft.WindowsAzure.Management.Common.Storage.CasePreservedDictionary, Microsoft.WindowsAzure.Management.Common.Storage" }, "properties": { "name": "My Testing", "enabled": true, "targetResourceUri": "/subscriptions/MySubScriptionID/resourceGroups/My-RG-Name/providers/Microsoft.Compute/virtualMachineScaleSets/nt1vm", "profiles": [ { "name": "Auto created scale condition 1", "capacity": { "minimum": "5", "maximum": "10", "default": "5" }, "rules": [ { "scaleAction": { "direction": "Decrease", "type": "ChangeCount", "value": "1", "cooldown": "PT5M" }, "metricTrigger": { "metricName": "Percentage CPU", "metricNamespace": "", "metricResourceUri": "/subscriptions//MySubScriptionID//resourceGroups/My-RG-Name/providers/Microsoft.Compute/virtualMachineScaleSets/nt1vm", "operator": "LessThan", "statistic": "Average", "threshold": 5, "timeAggregation": "Average", "timeGrain": "PT1M", "timeWindow": "PT5M" } } ], "fixedDate": { "timeZone": "Mountain Standard Time", "start": "2018-09-18T00:00:00.000Z", "end": "2018-09-21T23:59:00.000Z" } }, { "name": "Auto created scale condition", "capacity": { "minimum": "5", "maximum": "10", "default": "5" }, "rules": [ { "scaleAction": { "direction": "Increase", "type": "ChangeCount", "value": "1", "cooldown": "PT15M" }, "metricTrigger": { "metricName": "Percentage CPU", "metricNamespace": "", "metricResourceUri": "/subscriptions/MySubScriptionID/resourceGroups/My-RG-Name/providers/Microsoft.Compute/virtualMachineScaleSets/nt1vm", "operator": "GreaterThanOrEqual", "statistic": "Average", "threshold": 10, "timeAggregation": "Average", "timeGrain": "PT1M", "timeWindow": "PT5M" } } ] } ], "notifications": [ { "operation": "Scale", "email": { "sendToSubscriptionAdministrator": false, "sendToSubscriptionCoAdministrators": false, "customEmails": [ "" ] }, "webhooks": [] } ], "targetResourceLocation": "eastus" }, "id": "/subscriptions/MySubScriptionID/resourceGroups/My-RG-Name/providers/microsoft.insights/autoscalesettings/My Testing", "name": "My Testing", "type": "Microsoft.Insights/autoscaleSettings" }

观察:

  1. 我等待了5分钟以上(这是向外扩展选项的timeWindow值)。没有创建新节点。
  2. 等待10分钟,20分钟和30分钟后不会创建新节点。
  3. 当我在上述VMSS的azure门户中手动将节点数配置为6(从5个)(在“缩放”选项中)时,将创建该节点,并且一切都会按预期进行。

问题:

  1. 在上述自动缩放选项配置中,我在做什么?

1 个答案:

答案 0 :(得分:0)

看来我的定尺与定尺规则相冲突。一旦我删除了标尺,一切就开始起作用。