简体   繁体   English

Azure计算:操作系统修补,更新和停机时间

[英]Azure Compute : OS Patching, Updates and Downtime

We know that Azure Compute is PaaS so the Operating System (Windows Server 2008 R2) has to be patched and upgraded automatically. 我们知道Azure Compute是PaaS,因此必须自动修补和升级操作系统(Windows Server 2008 R2)。

I just wanted to know will there be any downtime during the patching or Compute upgradation...? 我只是想知道在修补或计算升级期间是否会出现停机时间......?

If you only have a single instance of a particular VM role, then yes - you'll have a short bit of downtime, as you need to be rebooted. 如果您只有一个特定VM角色的单个实例,则是 - 您将需要重新启动,因此您将有一小段停机时间。 Likewise, if the host OS is patched, you'll have a bit of downtime. 同样,如果主机操作系统已修补,您将有一些停机时间。

If you run two or more instances, then the SLA kicks in, because your instances are separated into different containers/network branches/etc. 如果您运行两个或更多实例,则SLA会启动,因为您的实例被分成不同的容器/网络分支/等。 These are fault domains. 这些是故障域。 So even if a network segment, router, or entire rack were to go offline, you'd have another instance somewhere else. 因此,即使网段,路由器或整个机架要脱机,您也可以在其他地方使用另一个实例。

During OS updates, your instances are divided into upgrade domains, so that they're not all upgraded at once. 在操作系统更新期间,您的实例将分为升级域,因此它们不会立即全部升级。 This leaves your service in an always-available state, as long as you have two or more instances of your roles. 只要您有两个或更多角色实例,这将使您的服务处于始终可用的状态。 For background processes that aren't customer-facing (say, in a worker role that simply reads from queues and processes queue items asynchronously), you can probably get away with a single instance of that role, provided you can handle the work load and that it would be ok to have occasional processing delays. 对于不面向客户的后台进程(例如,在简单地从队列中读取并异步处理队列项的辅助角色),您可以使用该角色的单个实例,只要您可以处理工作负载和偶尔处理延迟是可以的。

See this recent TechNet blog post for more details around fault domains and upgrade domains. 有关故障域和升级域的更多详细信息,请参阅最近的TechNet 博客文章

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM