Skip to content

Commit af46c3a

Browse files
committed
Add section on ephemeral disks
1 parent addf2fc commit af46c3a

File tree

1 file changed

+14
-1
lines changed

1 file changed

+14
-1
lines changed

articles/service-fabric/service-fabric-cluster-azure-deployment-preparation.md

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,10 +32,23 @@ The minimum size of VMs for each node type is determined by the [durability tier
3232

3333
The minimum number of VMs for the primary node type is determined by the [reliability tier][reliability] you choose.
3434

35-
See the minimum recommendations for [primary node types](service-fabric-cluster-capacity.md#primary-node-type---capacity-guidance), [stateful workloads on non-primary node types](service-fabric-cluster-capacity.md#non-primary-node-type---capacity-guidance-for-stateful-workloads), and [stateless workloads on non-primary node types](service-fabric-cluster-capacity.md#non-primary-node-type---capacity-guidance-for-stateless-workloads).
35+
See the minimum recommendations for [primary node types](service-fabric-cluster-capacity.md#primary-node-type---capacity-guidance), [stateful workloads on non-primary node types](service-fabric-cluster-capacity.md#non-primary-node-type---capacity-guidance-for-stateful-workloads), and [stateless workloads on non-primary node types](service-fabric-cluster-capacity.md#non-primary-node-type---capacity-guidance-for-stateless-workloads).
3636

3737
Any more than the minimum number of nodes should be based on the number of replicas of the application/services that you want to run in this node type. [Capacity planning for Service Fabric applications](service-fabric-capacity-planning.md) helps you estimate the resources you need to run your applications. You can always scale the cluster up or down later to adjust for changing application workload.
3838

39+
#### Use ephemeral OS disks for VM scale sets
40+
41+
*Ephemeral OS disks* are storage created on the local virtual machine (VM), and not saved to remote Azure Storage. They are recommended for all Service Fabric node types (Primary and Secondary), because compared to traditional persistent OS disks, ephemeral OS disks:
42+
43+
* Reduce read/write latency to OS disk
44+
* Enable faster reset/reimage node management operations
45+
* Reduce overall costs (the disks are free and incur no additional storage cost)
46+
47+
Ephemeral OS disks is not a specific Service Fabric feature, but rather a feature of the Azure *Virtual Machine scale sets* that are mapped to Service Fabric node types. See [Ephemeral OS disks for Azure VMs](../virtual-machines/windows/ephemeral-os-disks.md) for more info and instructions on configuring this VM feature.
48+
49+
> [!NOTE]
50+
> Be sure to select a VM size with a cache size equal or greater than the OS disk size of the VM itself, otherwise your ARM deployment might result in error (even if it's initially accepted).
51+
3952
### Select the durability and reliability levels for the cluster
4053
The durability tier is used to indicate to the system the privileges that your VMs have with the underlying Azure infrastructure. 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. 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. For advantages of the different levels and recommendations on which level to use and when, see [The durability characteristics of the cluster][durability].
4154

0 commit comments

Comments
 (0)