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
  • 每個節點類型 (大小、主要、網際網路對向、VM 數目等) 的屬性The properties of each of 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:

  • 您的應用程式是否有多個服務,而且其中是否有任何服務必須是公開或網際網路對向的服務?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 大小),且擁有可連線至網際網路之連接埠的 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 大小),且不連線至網際網路的 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. 這可讓每個節點類型都有不同的屬性,例如,網際網路連線或 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 的數目,以及 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. 預設持久性層級為 Bronze。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. 預設可靠性層級為 Silver。The default reliability tier is Silver. 如需詳細資訊,請參閱叢集的可靠性特性See The reliability characteristics of the cluster for more details.

在 Azure Resource Manager 範本中,主要節點類型會以 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. 預設持久性層級為 Bronze。The default durability tier is Bronze. 如需詳細資訊,請參閱叢集的持久性特性For more information, see The durability characteristics of the cluster.
  • 非主要節點類型的 VM 數目下限為 1。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 (例如 L32s、GS5、G5、DS15_v2、D15_v2)Full-node SKUs dedicated to a single customer (for example, L32s, GS5, G5, 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 單一核心或更多核心的 VMVMs of single core or above 可以延遲到 Service Fabric 叢集核准為止Can be delayed until approved by the Service Fabric cluster 無法延遲很長的期間Cannot be delayed for any significant period of time
BronzeBronze 11 全部All Service Fabric 叢集不會延遲Will not be delayed by the Service Fabric cluster 無法延遲很長的期間Cannot be delayed for any significant period of time

警告

執行 Bronze 持久性的節點類型「沒有權限」。Node types running with Bronze durability obtain no privileges. 這表示不會停止或延遲對您的無狀態工作負載造成影響的基礎結構作業 (可能會影響工作負載)。This means that infrastructure jobs that impact your stateless workloads will not be stopped or delayed, which might impact your workloads. 針對僅執行無狀態工作負載的節點類型,只能使用 Bronze。Use only Bronze for node types that run only stateless workloads. 對於生產工作負載,建議執行 Silver 或以上的層級。For production workloads, running Silver or above is recommended.

無論是任何持久性層級,虛擬機器擴展集上的解除配置作業都會終結叢集Regardless of any durability level, Deallocation operation on VM Scale Set will destroy the cluster

使用 Silver 或 Gold 持久性層級的優點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.

使用 Silver 或 Gold 持久性層級的缺點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.

使用 Silver 或 Gold 持久性層級的建議時機Recommendations for when to use Silver or Gold durability levels

針對所有裝載您預期會經常進行相應縮小 (減少 VM 執行個體計數),且偏好延遲部署作業並減少容量以簡化相應縮小作業之具狀態服務的節點類型,使用 Silver 或 Gold 持久性。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

  • 持久性層級為 Silver 或 Gold 的節點類型無法降級為 Bronze。Node types with durability levels of Silver or Gold cannot be downgraded to Bronze.
  • 從 Bronze 升級至 Silver 或 Gold 可能需要幾小時的時間。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.

針對您已設定為 Silver 或 Gold 耐久性層級之節點類型的作業建議。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 is inherently an unsafe operation and so should be avoided if possible. 以下為您可以遵循以避免發生常見問題的程序。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: Our recommendation is that you do not change VM SKU of the primary node type. 不支援變更主要節點類型的 SKU。Changing of the primary node type SKU is not supported. 如果是基於容量的原因而需要新的 SKU,我們建議新增更多執行個體。If the reason for the new SKU is capacity, we recommend adding more instances. 如果不能的話,從舊叢集建立新的叢集並還原應用程式狀態 (如果適用的話)。If that not possible, create a new cluster and restore application state (if applicable) from your old cluster. 您不需要還原任何系統服務狀態,它們會在您部署應用程式到新叢集時重新建立。You do not need to restore any system service state, they are recreated when you deploy your applications to your new cluster. 如果您在叢集上執行無狀態應用程式,請將您的應用程式部署至新叢集。If you are running stateless applications on your cluster, deploy your applications to the new cluster. 您不需還原任何項目。You have nothing to restore. 如果您決定採取不支援的做法,並想要變更 VM SKU,請修改虛擬機器擴展集模型定義以反映新的 SKU。If you decide to go the unsupported route and want to change the VM SKU, then make modifications to the virtual machine scale set Model definition to reflect the new SKU. 如果您的叢集只有單一節點類型,請確保所有具狀態應用程式會及時回應所有服務複本生命週期事件 (例如當組建中的複本陷入停滯),且您的服務複本重建期間為少於五分鐘 (針對 Silver 持久性層級)。If your cluster has only one node type, then make sure that all your stateful applications respond to all Service replica lifecycle events (like replica in build is stuck) in a timely fashion and that your service replica rebuild duration is less than five minutes (for Silver durability level).
  • 針對所有啟用 Gold 或 Silver 持久性的虛擬機器擴展集維持至少五個節點。Maintain a minimum count of five nodes for any virtual machine scale set that has durability level of Gold or Silver enabled.

  • 持久性層級為 Silver 或 Gold 的每個虛擬機器擴展集,都必須對應到它自己在 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 down 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. 在持久性層級為 Silver 或 Gold 的擴展集中,這些作業將會無限期地遭到封鎖。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:

  • Platinum - 執行包含七個目標複本集的系統服務Platinum - Run the System services with a target replica set count of seven
  • Gold - 執行包含七個目標複本集的系統服務Gold - Run the System services with a target replica set count of seven
  • Silver - 執行包含五個目標複本集的系統服務Silver - Run the System services with a target replica set count of five
  • Bronze - 執行包含三個目標複本集的系統服務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. 例如,針對具有 Gold 可靠性的叢集,會有 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 以及可靠性層級為 Silver。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:

  • 建議將叢集主要 NodeType 專用於系統服務,並使用放置限制式,將應用程式部署到次要 NodeTypes。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 是標準 D3 或標準 D3_V2 或對等項目,並搭配至少 14 GB 的本機 SSD。The recommended VM SKU is Standard D3 or Standard D3_V2 or equivalent with a minimum of 14 GB of local SSD.
  • 支援使用的最小 VM SKU 是標準 D1 或標準 D1_V2 或對等項目,並搭配至少 14 GB 的本機 SSD。The minimum supported use VM SKU is Standard D1 or Standard D1_V2 or equivalent with a minimum of 14 GB of local SSD.
  • 14-GB 的本機 SSD 是最低需求。The 14-GB local SSD is a minimum requirement. 我們建議的最小值為 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.
  • 基於效能理由,標準 A1 SKU 不支援生產工作負載。Standard A1 SKU is not supported for production workloads for performance reasons.
  • 不支援低優先順序的 VM。Low-priority VMs are not supported.

警告

在執行的叢集上變更主要節點虛擬機器 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 是標準 D3 或標準 D3_V2 或對等項目,並搭配至少 14 GB 的本機 SSD。The recommended VM SKU is Standard D3 or Standard D3_V2 or equivalent with a minimum of 14 GB of local SSD.
  • 支援使用的最小 VM SKU 是標準 D1 或標準 D1_V2 或對等項目,並搭配至少 14 GB 的本機 SSD。The minimum supported use VM SKU is Standard D1 or Standard D1_V2 or equivalent with a minimum of 14 GB of local SSD.
  • 局部核心 VM SKU 不支援生產工作負載,例如標準 A0。Partial core VM SKUs like Standard A0 are not supported for production workloads.
  • 基於效能理由,標準 A1 SKU 不支援生產工作負載。Standard A1 SKU is 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 是標準 D3 或標準 D3_V2 或對等項目。The recommended VM SKU is Standard D3 or Standard D3_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.
  • 基於效能理由,標準 A1 SKU 不支援生產工作負載。Standard A1 SKU is not supported for production workloads for performance reasons.

後續步驟Next steps

一旦您完成容量規劃並設定叢集之後,請閱讀︰Once you finish your capacity planning and set up a cluster, read the following: