【Azure App Services】多次操作App Service伸缩实例遇见限制操作记录

简介: 【Azure App Services】多次操作App Service伸缩实例遇见限制操作记录

问题描述

多次操作App Services,进行实例数的变化。达到限制后遇见报错:

错误的具体描述为:

{
   "status": "Failed",
   "error": {
       "code": "Conflict",
       "message": "You have exceeded the maximum amount of scale changes within the past hour(23 changes and limit is 20). Please retry later.",
       "details": [
           {
               "message": "You have exceeded the maximum amount of scale changes within the past hour(23 changes and limit is 20). Please retry later."
           },
           {
               "code": "Conflict"
           }
       ]
   }
}

 

问题解答

根据提示信息,“过去一小时内,您已超出Scale变化最大数量(23 次更改,限制为 20),请稍后重试。” 这个限制的目的是防止短时间内过度更改。

详细请参考以下文档:https://learn.microsoft.com/en-us/troubleshoot/azure/app-service/scaling-web-app-faq#i-m-unable-to-scale-up-scale-down-the-app-service-plan-due-to-the--you-have-exceeded-the-maximum-amount-of-scale-changes-within-the-past-hour--xx-changes-and-limit-is-xx---error--what-should-i-do--

若要避免此问题,请不要执行在一小时内释放超过 XX 个实例的缩放操作。 每次在纵向缩减操作期间释放实例时,该实例都会重新启动,以确保下一个App 服务计划可以获得干净的实例。 连续快速执行过多的缩放操作时,实例重启可能会导致其他应用服务出现性能问题。 因此,我们特意为缩放设置一种限制机制,以防止你快速连续执行超过可接受的限制的缩放操作。

I'm unable to scale up/scale down the App Service Plan due to the "You have exceeded the maximum amount of scale changes within the past hour (XX changes and limit is XX)" error. What should I do?

To avoid this issue, don't perform scaling operations that release more than XX instances in an hour. Every time you release an instance during a scale-down operation, the instance is rebooted to ensure the next App Service Plan can get a clean instance. When you perform too many scaling operations in quick succession, instance reboots can cause performance issues for other App Services. Therefore we intentionally put a throttling mechanism for scaling that prevents you from executing scaling operations more than the acceptable limit in quick succession.

 

 

参考资料

FAQs about scaling web apps in Azure App Service : https://learn.microsoft.com/en-us/troubleshoot/azure/app-service/scaling-web-app-faq

相关文章
|
8天前
|
C# Windows
【Azure App Service】在App Service for Windows上验证能占用的内存最大值
根据以上测验,当使用App Service内存没有达到预期的值,且应用异常日志出现OutOfMemory时,就需要检查Platform的设置是否位64bit。
32 11
|
9天前
|
JavaScript C++ 容器
【Azure Bot Service】部署NodeJS ChatBot代码到App Service中无法自动启动
2024-11-12T12:22:40.366223350Z Error: Cannot find module 'dotenv' 2024-11-12T12:40:12.538120729Z Error: Cannot find module 'restify' 2024-11-12T12:48:13.348529900Z Error: Cannot find module 'lodash'
33 11
|
3天前
|
缓存 容器 Perl
【Azure Container App】Container Apps 设置延迟删除 (terminationGracePeriodSeconds) 的解释
terminationGracePeriodSeconds : 这个参数的定义是从pod收到terminated signal到最终shutdown的最大时间,这段时间是给pod中的application 缓冲时间用来处理链接关闭,应用清理缓存的;并不是从idel 到 pod被shutdown之间的时间;且是最大时间,意味着如果application 已经gracefully shutdown,POD可能被提前terminated.
|
7天前
|
开发框架 监控 .NET
【Azure App Service】部署在App Service上的.NET应用内存消耗不能超过2GB的情况分析
x64 dotnet runtime is not installed on the app service by default. Since we had the app service running in x64, it was proxying the request to a 32 bit dotnet process which was throwing an OutOfMemoryException with requests >100MB. It worked on the IaaS servers because we had the x64 runtime install
|
5天前
|
Java 开发工具 Windows
【Azure App Service】在App Service中调用Stroage SDK上传文件时遇见 System.OutOfMemoryException
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
|
6天前
|
安全 Apache 开发工具
【Azure App Service】在App Service上关于OpenSSH的CVE2024-6387漏洞解答
CVE2024-6387 是远程访问漏洞,攻击者通过不安全的OpenSSh版本可以进行远程代码执行。CVE-2024-6387漏洞攻击仅应用于OpenSSH服务器,而App Service Runtime中并未使用OpenSSH,不会被远程方式攻击,所以OpenSSH并不会对应用造成安全风险。同时,如果App Service的系统为Windows,不会受远程漏洞影响!
|
30天前
|
JSON 小程序 JavaScript
uni-app开发微信小程序的报错[渲染层错误]排查及解决
uni-app开发微信小程序的报错[渲染层错误]排查及解决
452 7
|
30天前
|
小程序 JavaScript 前端开发
uni-app开发微信小程序:四大解决方案,轻松应对主包与vendor.js过大打包难题
uni-app开发微信小程序:四大解决方案,轻松应对主包与vendor.js过大打包难题
504 1
|
16天前
|
小程序 数据挖掘 UED
开发1个上门家政小程序APP系统,都有哪些功能?
在快节奏的现代生活中,家政服务已成为许多家庭的必需品。针对传统家政服务存在的问题,如服务质量不稳定、价格不透明等,我们历时两年开发了一套全新的上门家政系统。该系统通过完善信用体系、提供奖励机制、优化复购体验、多渠道推广和多样化盈利模式,解决了私单、复购、推广和盈利四大痛点,全面提升了服务质量和用户体验,旨在成为家政行业的领导者。
|
1月前
|
JavaScript 前端开发 小程序
uniapp一个人开发APP关键步骤和考虑因素
uniapp一个人开发APP关键步骤和考虑因素
121 1
uniapp一个人开发APP关键步骤和考虑因素

热门文章

最新文章