在更新应用程序设置时，Azure Functions是否会抛出503错误? [英] Does Azure Functions throw 503 errors while app settings are being updated?

问题描述

每当我更新功能应用程序的应用程序设置并单击Azure门户上的保存"按钮时，我都会观察到，此更改会暂时停止我的功能应用程序，同时将更改持久化给活动的工作者.我需要了解是否确实如此，或者我是否做出了错误的假设.

Whenever I update my application settings for a Function app and hit the Save button on Azure Portal, I observe that this action temporarily stops my function app while the changes are being persisted to the active worker(s). I need to understand if this is indeed the case or if I'm making a false assumption.

在门户中更新应用程序设置时，究竟会发生什么?

What happens exactly when app settings are updated in the portal?

• 正在更新活动工作者时抛出503

OR

• 另一位工作者专用于新的主机文件.一旦这名老工人活跃起来，他们就会停下来.

我不断收到503服务不可用错误.在生产中有什么方法可以避免这种情况?我需要定期旋转连接字符串/键，但是我不能承受不断中断服务的负担.

I keep getting 503 Service Unavailable errors. Is there any way to avoid this in production? I need to periodically rotate connection strings/keys, but I can't afford to disrupt the service constantly.

推荐答案

如果您更新应用程序设置，则会重新启动该应用程序.这就是为什么您会收到503错误的原因.

If you update the app settings, the app will be restarted. That's why you got 503 error.

通常在生产环境中，我们不会经常更改应用程序设置.

Usually in the production environment, we will not change the app settings frequently.

无论如何，为避免这种情况，您可以使用

Anyway, to avoid such situation, you can use the slot feature

这篇关于在更新应用程序设置时，Azure Functions是否会抛出503错误?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！