Service Fabric 群集容量规划注意事项Service Fabric cluster capacity planning considerations

对于任何生产部署,容量规划都是一个重要的步骤。For any production deployment, capacity planning is an important step. 下面是在规划过程中必须注意的一些事项。Here are some of the items that you have to consider as a part of that process.

  • 群集一开始需要的节点类型数目The number of node types your cluster needs to start out with
  • 每个节点类型的属性(大小、是否为主节点、是否面向 Internet、VM 数目,等等)The properties of each node type (size, primary, internet facing, number of VMs, etc.)
  • 群集的可靠性和持久性特征The reliability and durability characteristics of the cluster

备注

规划期间至少应该查看所有“不允许的”升级策略值。You should minimally review all Not Allowed upgrade policy values during planning. 这样可以确保正确设置值,并且可以减少不可更改的系统配置设置所导致的群集使用。This is to ensure that you set the values appropriately and to mitigate burning down of your cluster later because of unchangeable system configuration settings.

让我们简单地了解其中每一项。Let us briefly review each of these items.

群集一开始需要的节点类型数目The number of node types your cluster needs to start out with

首先,需要确定要创建的群集用于什么目的,First, you need to figure out what the cluster you are creating is going to be used for. 以及打算要将哪些类型的应用程序部署到此群集中。What kinds of applications you are planning to deploy into this cluster? 如果不清楚群集的用途,则很可能还未准备好进入容量规划流程。If you are not clear on the purpose of the cluster, you are most likely not yet ready to enter the capacity planning process.

确定群集一开始需要的节点类型数目。Establish the number of node types your cluster needs to start out with. 每个节点类型将映射到虚拟机规模集。Each node type is mapped to a virtual machine scale set. 然后,每个节点类型可以独立扩展或缩减、打开不同的端口集,并可以有不同的容量指标。Each node type can then be scaled up or down independently, have different sets of ports open, and can have different capacity metrics. 因此,节点类型数目的确定基本上可归结为以下考虑因素:So the decision of the number of node types essentially comes down to the following considerations:

  • 应用程序是否有多个服务,其中是否有任何服务需面向公众或面向 Internet?Does your application have multiple services, and do any of them need to be public or internet facing? 典型的应用程序包含可接收客户端输入的前端网关服务,以及一个或多个与前端服务通信的后端服务。Typical applications contain a front-end gateway service that receives input from a client and one or more back-end services that communicate with the front-end services. 因此,在此情况下,必须至少有两个节点类型。So in this case, you end up having at least two node types.

  • (构成应用程序的)服务是否有不同的基础结构要求,例如,更多的 RAM 或更高的 CPU 周期?Do your services (that make up your application) have different infrastructure needs such as greater RAM or higher CPU cycles? 例如,假设要部署的应用程序包含前端服务和后端服务。For example, let us assume that the application that you want to deploy contains a front-end service and a back-end service. 前端服务可以在容量较小(如 D2 的 VM 大小)且向 Internet 开放了端口的 VM 上运行。The front-end service can run on smaller VMs (VM sizes like D2) that have ports open to the internet. 但是,后端服务是计算密集型的服务,需要放在容量较大(D4、D6、D15 等的 VM 大小)且不面向 Internet 的 VM 上运行。The back-end service, however, is computation intensive and needs to run on larger VMs (with VM sizes like D4, D6, D15) that are not internet facing.

    在本示例中,可以决定将所有服务都放在一个节点类型上,但我们建议将它们分别放在群集中的两个节点类型上。In this example, although you can decide to put all the services on one node type, we recommended that you place them in a cluster with two node types. 这样,每个节点类型都有不同的属性,例如,Internet 连接或 VM 大小。This allows each node type to have distinct properties such as internet connectivity or VM size. 也可以单独缩放 VM 的数目。The number of VMs can be scaled independently, as well.

  • 由于无法预见未来,因此,请利用所知道的事实,选择应用程序一开始需要的节点类型数目。Because you cannot predict the future, go with facts you know, and choose the number of node types that your applications need to start with. 以后,随时可以添加或删除节点类型。You can always add or remove node types later. Service Fabric 群集必须至少有一个节点类型。A Service Fabric cluster must have at least one node type.

每个节点类型的属性The properties of each node type

节点类型 相当于云服务中的角色。The node type can be seen as equivalent to roles in Cloud Services. 节点类型定义 VM 大小、VM 数目及其属性。Node types define the VM sizes, the number of VMs, and their properties. 在 Service Fabric 群集中定义的每个节点类型映射到虚拟机规模集Every node type that is defined in a Service Fabric cluster maps to a virtual machine scale set.
每个节点类型是不同的规模集,可以独立扩展或缩减,可以打开不同的端口集,并且有不同的容量指标。Each node type is a distinct scale set and can be scaled up or down independently, have different sets of ports open, and have different capacity metrics. 若要详细了解节点类型和虚拟机规模集之间关系、如何 RDP 到任一实例、如何打开新的端口等,请参阅 Service Fabric 群集节点类型For more information about the relationships between node types and virtual machine scale sets, how to RDP into one of the instances, how to open new ports, and so on, see Service Fabric cluster node types.

Service Fabric 群集可以包含不止一个节点类型。A Service Fabric cluster can consist of more than one node type. 在这种情况下,群集包含一个主节点类型以及一个或多个非主节点类型。In that event, the cluster consists of one primary node type and one or more non-primary node types.

对于 SF 应用程序,单节点类型无法可靠地扩展到每个虚拟机规模集超过 100 个节点;要可靠地实现超过 100 个节点,需要添加其他虚拟机规模集。A single node type cannot reliably scale beyond 100 nodes per virtual machine scale set for SF applications; achieving greater than 100 nodes reliably, will require you to add additional virtual machine scale sets.

主节点类型Primary node type

Service Fabric 系统服务(例如,群集管理器服务或图像存储服务)是主节点类型。The Service Fabric system services (for example, the Cluster Manager service or Image Store service) are placed on the primary node type.

具有两个节点类型的群集的屏幕截图

  • 主节点类型的 VM 大小下限取决于选择的持久性层The minimum size of VMs for the primary node type is determined by the durability tier you choose. 默认持续性层为“青铜”。The default durability tier is Bronze. 请参阅群集的持续性特征以了解更多详细信息。See The durability characteristics of the cluster for more details.
  • 主节点类型的 VM 数目下限取决于选择的可靠性层The minimum number of VMs for the primary node type is determined by the reliability tier you choose. 默认可靠性层为“白银”。The default reliability tier is Silver. 请参阅群集的可靠性特征以获取更多详细信息。See The reliability characteristics of the cluster for more details.

在 Azure 资源管理器模板中,主节点类型在节点类型定义下配置了 isPrimary 属性。From the Azure Resource Manager template, the primary node type is configured with the isPrimary attribute under the node type definition.

非主节点类型Non-primary node type

包含多个节点类型的群集有一个主节点类型,剩余的是非主节点类型。In a cluster with multiple node types, there is one primary node type and the rest are non-primary.

  • 非主节点类型的“VM 大小下限”取决于你选择的“持续性层” 。The minimum size of VMs for non-primary node types is determined by the durability tier you choose. 默认持续性层为“青铜”。The default durability tier is Bronze. 有关详细信息,请参阅群集的持续性特征For more information, see The durability characteristics of the cluster.
  • 非主节点类型的“VM 数量下限”为一。The minimum number of VMs for non-primary node types is one. 但是,应该根据想要在此节点类型中运行的应用程序/服务的副本数目选择此数目。However, you should choose this number based on the number of replicas of the application/services that you want to run in this node type. 部署群集之后,节点类型中的 VM 数目可能会增加。The number of VMs in a node type can be increased after you have deployed the cluster.

群集的持久性特征The durability characteristics of the cluster

持久性层用于向系统指示 VM 对于基本 Azure 基础结构拥有的权限。The durability tier is used to indicate to the system the privileges that your VMs have with the underlying Azure infrastructure. 在主节点类型中,此权限可让 Service Fabric 暂停影响系统服务及有状态服务的仲裁要求的任何 VM 级别基础结构请求(例如,VM 重启、VM 重置映像或 VM 迁移)。In the primary node type, this privilege allows Service Fabric to pause any VM level infrastructure request (such as a VM reboot, VM reimage, or VM migration) that impact the quorum requirements for the system services and your stateful services. 在非主节点类型中,此特权可让 Service Fabric 暂停影响其中运行的有状态服务的仲裁要求的任何 VM 级别基础结构请求,例如,VM 重新启动、VM 重置映像、VM 迁移,等等。In the non-primary node types, this privilege allows Service Fabric to pause any VM level infrastructure requests (such as VM reboot, VM reimage, and VM migration) that impact the quorum requirements for your stateful services.

持续性层Durability tier 所需 VM 数量下限Required minimum number of VMs 受支持的 VM SKUSupported VM SKUs 你对虚拟机规模集所做的更新Updates you make to your virtual machine scale set Azure 启动的更新和维护Updates and maintenance initiated by Azure
GoldGold 55 专用于单个客户的完整节点 SKU(例如 DS15_v2、D15_v2)Full-node SKUs dedicated to a single customer (for example, DS15_v2, D15_v2) 可延迟到 Service Fabric 群集批准Can be delayed until approved by the Service Fabric cluster 每个 UD 可以暂停 2 小时,提供额外的时间让副本从之前的故障中恢复Can be paused for 2 hours per UD to allow additional time for replicas to recover from earlier failures
SilverSilver 55 单核或更多核心的 VM,至少 50 GB 的本地 SSDVMs of single core or above with at least 50 GB of local SSD 可延迟到 Service Fabric 群集批准Can be delayed until approved by the Service Fabric cluster 任何时候都无法延迟Cannot be delayed for any significant period of time
BronzeBronze 11 VM,至少 50 GB 的本地 SSDVMs with at least 50 GB of local SSD 不会因为 Service Fabric 群集延迟Will not be delayed by the Service Fabric cluster 任何时候都无法延迟Cannot be delayed for any significant period of time

警告

以青铜级持续性运行的节点类型不具有任何特权。Node types running with Bronze durability obtain no privileges. 这意味着,不会停止或延迟对有状态工作负荷产生影响的基础结构作业,这可能影响工作负荷。This means that infrastructure jobs that impact your stateful workloads will not be stopped or delayed, which might impact your workloads. 对仅运行无状态工作负荷的节点类型仅使用“青铜”。Use only Bronze for node types that run only stateless workloads. 对于生产工作负荷,建议运行“白银”或以上级别。For production workloads, running Silver or above is recommended.

无论任何持续性级别,VM 规模集上的释放操作都将破坏群集Regardless of any durability level, Deallocation operation on VM Scale Set will destroy the cluster

使用“白银”或“黄金”耐久性级别的优点Advantages of using Silver or Gold durability levels

  • 减少了“缩小规模”操作所需的步骤数(即自动调用节点停用和 Remove-ServiceFabricNodeState)。Reduces the number of required steps in a scale-in operation (that is, node deactivation and Remove-ServiceFabricNodeState is called automatically).
  • 减少了由于客户启动的就地 VM SKU 更改操作或 Azure 基础结构操作而导致的数据丢失的风险。Reduces the risk of data loss due to a customer-initiated in-place VM SKU change operation or Azure infrastructure operations.

使用“白银”或“黄金”耐久性级别的缺点Disadvantages of using Silver or Gold durability levels

  • 部署到虚拟机规模集和其他相关 Azure 资源可能会由于群集中的问题或基础结构级别的问题而延迟、超时或被完全阻止。Deployments to your virtual machine scale set and other related Azure resources can be delayed, can time out, or can be blocked entirely by problems in your cluster or at the infrastructure level.
  • 由于 Azure 基础结构操作期间发生的自动节点停用而增加了副本生命周期事件(例如,主交换)的数量。Increases the number of replica lifecycle events (for example, primary swaps) due to automated node deactivations during Azure infrastructure operations.
  • 执行 Azure 平台的软件更新或硬件维护活动时,将节点暂停服务一段时间。Takes nodes out of service for periods of time while Azure platform software updates or hardware maintenance activities are occurring. 在这些活动期间,你可能会看到状态为“正在禁用”/“已禁用”的节点。You may see nodes with status Disabling/Disabled during these activities. 这会暂时降低群集的容量,但不应影响群集或应用程序的可用性。This reduces the capacity of your cluster temporarily, but should not impact the availability of your cluster or applications.

有关何时使用“白银”或“黄金”持续性级别的建议Recommendations for when to use Silver or Gold durability levels

对于托管要频繁缩小规模(减小 VM 实例计数)的有状态服务,并且你愿意延迟部署操作并减少容量以利于简化这些“缩小规模”操作的所有节点类型,请使用“白银”或“黄金”耐久性。Use Silver or Gold durability for all node types that host stateful services you expect to scale-in (reduce VM instance count) frequently, and you would prefer that deployment operations be delayed and capacity to be reduced in favor of simplifying these scale-in operations. “扩大规模”的情况(添加 VM 实例)不会受所选耐久性层的影响,只有“缩小规模”的情况才受其影响。The scale-out scenarios (adding VMs instances) do not play into your choice of the durability tier, only scale-in does.

更改耐久性级别Changing durability levels

  • 耐久性级别为“白银”或“黄金”的节点类型不能降级为“青铜”。Node types with durability levels of Silver or Gold cannot be downgraded to Bronze.
  • 从“青铜”升级到“白银”或“黄金”可能需要几个小时。Upgrading from Bronze to Silver or Gold can take a few hours.
  • 更改耐久性级别时,请务必在虚拟机规模集资源中的 Service Fabric 扩展配置以及 Service Fabric 群集资源中的节点类型定义中同时进行更新。When changing durability level, be sure to update it in both the Service Fabric extension configuration in your virtual machine scale set resource, and in the node type definition in your Service Fabric cluster resource. 这些值必须匹配。These values must match.

适用于已设置为“白银”或“黄金”耐久性级别的节点类型的操作建议。Operational recommendations for the node type that you have set to silver or gold durability level.

  • 使群集和应用程序在任何时间都正常工作,并确保应用程序及时响应所有服务副本生命周期事件(例如,生成副本时出现停滞)。Keep your cluster and applications healthy at all times, and make sure that applications respond to all Service replica lifecycle events (like replica in build is stuck) in a timely fashion.

  • 采用更安全的方式进行 VM SKU 更改(增大/减小):更改虚拟机规模集的 VM SKU 需要执行多个步骤并进行多项考虑。Adopt safer ways to make a VM SKU change (Scale up/down): Changing the VM SKU of a virtual machine scale set requires a number of steps and considerations. 可以遵循以下过程来避免常见问题。Here is the process you can follow to avoid common issues.

    • 对于非主节点类型: 建议创建新的虚拟机规模集,修改服务放置约束以包括新的虚拟机规模集/节点类型,然后将旧的虚拟机规模集实例计数降低到零,一次一个节点(这是为了确保删除节点不会影响群集的可靠性)。For non-primary node types: It is recommended that you create new virtual machine scale set, modify the service placement constraint to include the new virtual machine scale set/node type and then reduce the old virtual machine scale set instance count to zero, one node at a time (this is to make sure that removal of the nodes do not impact the reliability of the cluster).
    • 对于主节点类型: 如果所选 VM SKU 达到容量限制,而你希望增大其容量,请按主节点类型垂直缩放指南操作。For the primary node type: If the VM SKU you have selected is at capacity and you would like to change to a larger VM SKU, follow our guidance on vertical scaling for a primary node type.
  • 为任何已启用“黄金”或“白银”耐久性级别的虚拟机规模集保留至少五个节点。Maintain a minimum count of five nodes for any virtual machine scale set that has durability level of Gold or Silver enabled.

  • 持续性级别为“白银”或“黄金”的每个虚拟机规模集,在 Service Fabric 群集中都必须映射到其自己的节点类型。Each virtual machine scale set with durability level Silver or Gold must map to its own node type in the Service Fabric cluster. 将多个虚拟机规模集映射到单个节点类型,将阻碍 Service Fabric 群集和 Azure 基础结构间的协调正常工作。Mapping multiple virtual machine scale sets to a single node type will prevent coordination between the Service Fabric cluster and the Azure infrastructure from working properly.

  • 不要删除随机 VM 实例,请始终使用虚拟机规模集横向缩减功能。Do not delete random VM instances, always use virtual machine scale set scale in feature. 删除随机 VM 实例可能会造成分布在 UD 和 FD 的 VM 实例失衡。The deletion of random VM instances has a potential of creating imbalances in the VM instance spread across UD and FD. 这一失衡可能会对系统在服务实例/服务副本之间进行适当负载均衡的能力产生负面影响。This imbalance could adversely affect the systems ability to properly load balance amongst the service instances/Service replicas.

  • 如果使用自动缩放,请设置规则,以便一次只有一个节点执行“缩小规模”操作(删除 VM 实例)。If using Autoscale, then set the rules such that scale in (removing of VM instances) are done only one node at a time. 一次减少多个实例是不安全的。Scaling down more than one instance at a time is not safe.

  • 删除或解除分配主节点类型上的 VM 时,决不应当将已分配的 VM 的数量降低到可靠性层需要的数量之下。If deleting or deallocating VMs on the primary node type, you should never reduce the count of allocated VMs below what the reliability tier requires. 在耐久性级别为“白银”或“黄金”的规模集中,这些操作会被无限期阻止。These operations will be blocked indefinitely in a scale set with a durability level of Silver or Gold.

群集的可靠性特征The reliability characteristics of the cluster

可靠性层用于设置想要在此群集中的主节点类型上运行的系统服务副本数。The reliability tier is used to set the number of replicas of the system services that you want to run in this cluster on the primary node type. 副本数越大,群集中的系统服务越可靠。The more the number of replicas, the more reliable the system services are in your cluster.

可靠性层可以采用以下值:The reliability tier can take the following values:

  • 白金 - 运行包含 9 个目标副本集的系统服务Platinum - Run the System services with a target replica set count of nine
  • 黄金 - 运行包含 7 个目标副本集的系统服务Gold - Run the System services with a target replica set count of seven
  • 白银 - 运行包含 5 个目标副本集的系统服务Silver - Run the System services with a target replica set count of five
  • 青铜 - 运行包含 3 个目标副本集的系统服务Bronze - Run the System services with a target replica set count of three

备注

选择的可靠性层决定了主节点类型必须具有的最少节点数。The reliability tier you choose determines the minimum number of nodes your primary node type must have.

针对可靠性层的建议Recommendations for the reliability tier

扩大或减小群集规模(所有节点类型中的 VM 实例总和)时,必须将群集的可靠性从一个层更新到另一层。When you increase or decrease the size of your cluster (the sum of VM instances in all node types), you must update the reliability of your cluster from one tier to another. 这样做会触发更改系统服务副本集计数所需的群集升级。Doing this triggers the cluster upgrades needed to change the system services replica set count. 等待升级完成,然后对群集做出其他任何更改,例如添加节点。Wait for the upgrade in progress to complete before making any other changes to the cluster, like adding nodes. 可以在 Service Fabric Explorer 中运行 Get-ServiceFabricClusterUpgrade 来监视升级进度You can monitor the progress of the upgrade on Service Fabric Explorer or by running Get-ServiceFabricClusterUpgrade

下面是有关选择可靠性层的建议。Here is the recommendation on choosing the reliability tier. 种子节点数也设置为可靠性层的最小节点数。The number of seed nodes is also set to the minimum number of nodes for a reliability tier. 例如,具有黄金级可靠性的群集有 7 个种子节点。For example, for a cluster with Gold reliability there are 7 seed nodes.

群集节点数Number of cluster nodes 可靠性层Reliability Tier
11 不要指定“可靠性层”参数,系统会计算该参数Do not specify the Reliability Tier parameter, the system calculates it
33 BronzeBronze
5 或 65 or 6 SilverSilver
7 或 87 or 8 GoldGold
9 及以上9 and up PlatinumPlatinum

主节点类型 - 容量指导Primary node type - capacity guidance

下面是用于规划主节点类型容量的指导:Here is the guidance for planning the primary node type capacity:

  • 要在 Azure 中运行任何生产工作负荷的 VM 实例数: 必须将最小主节点类型大小指定为 5,将可靠性层指定为“银级”。Number of VM instances to run any production workload in Azure: You must specify a minimum Primary Node type size of 5 and a Reliability Tier of Silver.
  • 要在 Azure 中运行测试工作负荷的 VM 实例数: 可以将最小主节点类型大小指定为 1 或 3。Number of VM instances to run test workloads in Azure You can specify a minimum primary node type size of 1 or 3. 单节点群集,采用特殊配置来运行,因此不支持对该群集进行扩展。The one node cluster, runs with a special configuration and so, scale out of that cluster is not supported. 单节点群集,不具备可靠性,因此,必须在 Resource Manager 模板中删除/不指定该配置(单纯不设置配置值还不够)。The one node cluster, has no reliability and so in your Resource Manager template, you have to remove/not specify that configuration (not setting the configuration value is not enough). 如果设置通过门户设置的单节点群集,则系统会自动处理该配置。If you set up the one node cluster set up via portal, then the configuration is automatically taken care of. 不支持使用单节点群集和三节点群集运行生产工作负荷。One and three node clusters are not supported for running production workloads.
  • VM SKU: 主节点类型是运行系统服务的位置,因此,在为它选择 VM SKU 时,必须考虑到你要在群集中放置的总峰值负载。VM SKU: Primary node type is where the system services run, so the VM SKU you choose for it, must take into account the overall peak load you plan to place into the cluster. 下面这个类比用来说明此处我要表达的意思 - 将主节点类型想象成你的“肺”,它向你的大脑提供氧气,如果大脑不能获得足够的氧气,你的身体会感到痛苦。Here is an analogy to illustrate what I mean here - Think of the primary node type as your "Lungs", it is what provides oxygen to your brain, and so if the brain does not get enough oxygen, your body suffers.

由于群集的容量需求是由你计划在群集中运行的工作负荷决定的,因此,我们无法针对具体工作负荷提供定性指导,但是下面的宽泛指导可帮助你入门Since the capacity needs of a cluster is determined by workload you plan to run in the cluster, we cannot provide you with qualitative guidance for your specific workload, however here is the broad guidance to help you get started

对于生产工作负荷:For production workloads:

  • 建议将群集的主要节点类型提供给系统服务,使用位置约束将应用程序部署到辅助节点类型。It's recommended to dedicate your clusters primary NodeType to system services, and use placement constraints to deploy your application to secondary NodeTypes.

  • 建议的 VM SKU 为标准 D2_V2 或与之相当的类型,使用至少 50 GB 的本地 SSD。The recommended VM SKU is Standard D2_V2 or equivalent with a minimum of 50 GB of local SSD.

  • 支持使用的最小 VM SKU 为 Standard_D2_V3 或 Standard D1_V2 或与之相当的类型,使用至少 50 GB 的本地 SSD。The minimum supported use VM SKU is Standard_D2_V3 or Standard D1_V2 or equivalent with a minimum of 50 GB of local SSD.

  • 建议至少为 50 GB。Our recommendation is a minimum of 50 GB. 对于你的工作负荷,尤其是在运行 Windows 容器时,需要更大的磁盘。For your workloads, especially when running Windows containers, larger disks are required.

  • 生产工作负荷不支持不完整的核心 VM SKU,例如标准 A0。Partial core VM SKUs like Standard A0 are not supported for production workloads.

  • 由于性能原因,不支持将一系列 VM SKU 用于生产工作负荷。A series VM SKUs are not supported for production workloads for performance reasons.

警告

在正在运行的群集上更改主节点 VM SKU 大小是一种扩展操作,并在虚拟机规模集横向扩展文档中进行了说明。Changing the primary node VM SKU size on a running cluster, is a scaling operation, and documented in Virtual Machine Scale Set scale out documentation.

非主节点类型 - 针对有状态工作负荷的容量指导Non-primary node type - capacity guidance for stateful workloads

本指南适用于使用 Service Fabric 可靠集合或可靠角色(在非主节点类型上运行)的有状态工作负荷。This guidance is for stateful Workloads using Service fabric reliable collections or reliable Actors that you are running in the non-primary node type.

VM 实例数: 对于有状态生产工作负荷,建议使用最小值和目标副本计数 5 运行它们。Number of VM instances: For production workloads that are stateful, it is recommended that you run them with a minimum and target replica count of 5. 这意味着,在稳定的状态下,最终在每个容错域和升级域中都将具有一个副本(来自副本集)。This means that in steady state you end up with a replica (from a replica set) in each fault domain and upgrade domain. 主节点类型的整体可靠性层概念实际上只是一种为系统服务指定此设置的方法。The whole reliability tier concept for the primary node type is a way to specify this setting for system services. 因此,这一注意事项同样适用于有状态服务。So the same consideration applies to your stateful services as well.

因此,对于生产工作负荷,如果在节点中运行有状态工作负荷,建议使用的最小非主节点类型大小为 5。So for production workloads, the minimum recommended non-Primary Node type size is 5, if you are running stateful workloads in it.

VM SKU: 这是运行应用程序服务的节点类型,因此,为其选择的 VM SKU 必须将你计划在每个节点中放置的峰值负荷考虑在内。VM SKU: This is the node type where your application services are running, so the VM SKU you choose for it, must take into account the peak load you plan to place into each Node. 节点类型的容量需求是由你计划在群集中运行的工作负荷决定的,因此,我们无法针对具体工作负荷提供定性指导,但是下面的宽泛指导可帮助你入门The capacity needs of the node type, is determined by workload you plan to run in the cluster, so we cannot provide you with qualitative guidance for your specific workload, however here is the broad guidance to help you get started

对于生产工作负荷For production workloads

  • 建议的 VM SKU 为标准 D2_V2 或与之相当的类型,使用至少 50 GB 的本地 SSD。The recommended VM SKU is Standard D2_V2 or equivalent with a minimum of 50 GB of local SSD.
  • 支持使用的最小 VM SKU 为 Standard_D2_V3 或 Standard D1_V2 或与之相当的类型,使用至少 50 GB 的本地 SSD。The minimum supported use VM SKU is Standard_D2_V3 or Standard D1_V2 or equivalent with a minimum of 50 GB of local SSD.
  • 生产工作负荷不支持不完整的核心 VM SKU,例如标准 A0。Partial core VM SKUs like Standard A0 are not supported for production workloads.
  • 由于性能原因,不支持将一系列 VM SKU 用于生产工作负荷。A series VM SKUs are not supported for production workloads for performance reasons.

非主节点类型 - 针对无状态工作负荷的容量指导Non-primary node type - capacity guidance for stateless workloads

在非主节点类型上运行的无状态工作负荷指南。This guidance of stateless Workloads that you are running on the non-primary node type.

VM 实例数: 对于无状态生产工作负荷,支持的最小非主节点类型大小为 2。Number of VM instances: For production workloads that are stateless, the minimum supported non-Primary Node type size is 2. 这允许运行应用程序的两个无状态实例,并允许服务在某个 VM 实例丢失的情况下继续运行。This allows you to run you two stateless instances of your application and allowing your service to survive the loss of a VM instance.

VM SKU: 这是运行应用程序服务的节点类型,因此,为其选择的 VM SKU 必须将你计划在每个节点中放置的峰值负荷考虑在内。VM SKU: This is the node type where your application services are running, so the VM SKU you choose for it, must take into account the peak load you plan to place into each Node. 节点类型的容量需求是由你计划在群集中运行的工作负荷决定的。The capacity needs of the node type is determined by the workload you plan to run in the cluster. 我们无法针对你的具体工作负荷提供定性指导。We cannot provide you with qualitative guidance for your specific workload. 但是,下面提供了可帮助你入门的宽泛指导。However, here is the broad guidance to help you get started.

对于生产工作负荷For production workloads

  • 建议的 VM SKU 为Standard D2_V2 或相当的容量。The recommended VM SKU is Standard D2_V2 or equivalent.
  • 支持使用的最小 VM SKU 为标准 D1、标准 D1_V2 或相当的容量。The minimum supported use VM SKU is Standard D1 or Standard D1_V2 or equivalent.
  • 生产工作负荷不支持不完整的核心 VM SKU,例如标准 A0。Partial core VM SKUs like Standard A0 are not supported for production workloads.
  • 由于性能原因,不支持将一系列 VM SKU 用于生产工作负荷。A series VM SKUs are not supported for production workloads for performance reasons.

后续步骤Next steps

完成容量规划并设置群集后,请阅读以下文章:Once you finish your capacity planning and set up a cluster, read the following: