You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/service-fabric/service-fabric-cluster-resource-manager-sensitivity.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ For instance, in the scenario as listed in the table, Node 1 is under node capac
23
23
|Node 1 |150/100 |50 |50 |50 |
24
24
|Node 2 |0/100 ||||
25
25
26
-
While in the following case, two MSRs with load of 60 each collocates on Node 1, leading to the Node 1 capacity violation. The Node 2 has space of 80 with only one Non-MSR (load = 20) placed on it. One of the MSRs on node 1 has to be moved to node 2 as there is no Non-MSR present on node 1.
26
+
While in the following case, two MSRs with load of 60 each collocates on Node 1, leading to the capacity violation of Node 1. Node 2 has space of 80 with only one Non-MSR (load = 20) placed on it. One of the MSRs on node 1 has to be moved to node 2 as there is no Non-MSR present on node 1 to be moved to fix violation.
27
27
28
28
|Node |Node Load/Capacity |MSR Service 1 Load |MSR Service 2 Load|Non-MSR Service Load |
29
29
|:------|:------|:------|:------|:------|
@@ -32,15 +32,15 @@ While in the following case, two MSRs with load of 60 each collocates on Node 1,
32
32
33
33
The sensitivity feature allows multiple MSRs to collocate on the same node. Nevertheless, an excessive number of MSRs may result in node capacity violation. Thus, along with `IsMaximumSensitivity`, the feature introduces the maximum load to the metric to ensure the sum of maximum loads for each metric is smaller than or equal to the node capacity of that metric. With this upper bound set, CRM can safely collocate multiple MSRs on the same node, avoiding the scenario that the only way to fix node capacity violation is to move a max sensitivity replica.
34
34
35
-
Let's say that two customer metrics are defined for cluster node: ACU (Application CPU Usage) and IDSU (Instance Disk Usage). The node capacities for ACU and IDSU are **100 vCores** and **4 TB** respectively.
35
+
Let's say that two customer metrics are defined for cluster node: MetricA and MetricB. The node capacities for MetricA and MetricB are **100** and **4** respectively.
36
36
37
-
The table here shows a few examples regarding the collocation of maximum sensitivity replicas. For the three scenarios listed in the table, assume there already exists one max sensitivity replica on a node. Whether more MSRs can be placed on this node depends on space left on the node and resources needed for new MSRs.
38
-
1. More MSRs can be placed on this node as long as it does not cause node load or MaxLoad capacity violation. (that is, `ACU (Max)Load <= 50 vCores && IDSU (Max)Load <= 2 TB`).
39
-
2. No other MSR can be placed on this node as the MaxLoads for both ACU and IDSU reach to their node MaxLoad capacities.
40
-
3. No other MSR can be placed on this node as the MaxLoad for IDSU reaches to its node MaxLoad capacity though there exists room from the perspective of ACU.
37
+
The table here shows a few examples regarding the collocation of maximum sensitivity replicas. For the three scenarios listed in the table, assume there already exists one max sensitivity replica on a node and MaxLoad for either Metric A or MetricB is required to be positive. Whether more MSRs can be placed on this node depends on space left on the node and resources needed for new MSRs.
38
+
1. More MSRs can be placed on this node as long as it does not cause node load or MaxLoad capacity violation. (that is, `MetricA (Max)Load <= 50 && MetricB (Max)Load <= 2`).
39
+
2. No other MSR can be placed on this node as the MaxLoads for both MetricA and MetricB reach to their node MaxLoad capacities.
40
+
3. No other MSR can be placed on this node as the MaxLoad for MetricB reaches to its node MaxLoad capacity though there exists room from the perspective of MetricA.
41
41
42
42
43
-
|Scenario # |ACU Load |IDSU Load|IsMaximumSensitivity |ACU MaxLoad |IDSU MaxLoad |Can another MSR be placed on this node?|
43
+
|Scenario # |MetricA Load |MetricB Load|IsMaximumSensitivity |MetricA MaxLoad |MetricB MaxLoad |Can another MSR be placed on this node?|
0 commit comments