Skip to content

Commit 4162218

Browse files
adjusting the wording according to the capacity doc
1 parent 1d4e73f commit 4162218

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/service-fabric/service-fabric-production-readiness-checklist.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,8 @@ Is your application and cluster ready to take production traffic? Running and te
1818
1. Use a D2v2 or higher SKU for the primary node type. It is recommended to pick a SKU with at least 50 GB hard disk capacity.
1919
1. Production clusters must be [secure](service-fabric-cluster-security.md). For an example of setting up a secure cluster, see this [cluster template](https://github.com/Azure-Samples/service-fabric-cluster-templates/tree/master/7-VM-Windows-3-NodeTypes-Secure-NSG). Use common names for certificates and avoid using self signed certs.
2020
1. Add [resource constraints on containers and services](service-fabric-resource-governance.md), so that they don't consume more than 75% of node resources.
21-
1. Understand and set the [durability level](service-fabric-cluster-capacity.md#durability-characteristics-of-the-cluster). Silver or higher durability level is recommended for node types running stateful workloads.
22-
1. Understand and pick the [reliability level](service-fabric-cluster-capacity.md#reliability-characteristics-of-the-cluster) of the node type. Silver or higher reliability is recommended.
21+
1. Understand and set the [durability level](service-fabric-cluster-capacity.md#durability-characteristics-of-the-cluster). Silver or higher durability level is recommended for node types running stateful workloads, and required for production.
22+
1. Understand and pick the [reliability level](service-fabric-cluster-capacity.md#reliability-characteristics-of-the-cluster) of the node type. Silver or higher reliability is recommended, and required for production.
2323
1. Load and scale test your workloads to identify [capacity requirements](service-fabric-cluster-capacity.md) for your cluster.
2424
1. Your services and applications are monitored and application logs are being generated and stored, with alerting. For example, see [Add logging to your Service Fabric application](service-fabric-how-to-diagnostics-log.md) and [Monitor containers with Azure Monitor logs](service-fabric-diagnostics-oms-containers.md).
2525
1. The cluster is monitored with alerting (for example, with [Azure Monitor logs](service-fabric-diagnostics-event-analysis-oms.md)).

0 commit comments

Comments
 (0)