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/iot-operations/manage-mqtt-connectivity/howto-configure-availability-scale.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,10 +36,11 @@ The `cardinality` field is a nested field that has these subfields:
36
36
37
37
-`frontend`: This subfield defines the settings for the frontend pods, such as:
38
38
-`replicas`: The number of frontend pods to deploy. This subfield is required if the `mode` field is set to `distributed`.
39
+
-`workers`: The number of workers to deploy per frontend, currently it must be set to `1`. This subfield is required if the `mode` field is set to `distributed`.
39
40
-`backendChain`: This subfield defines the settings for the backend chains, such as:
40
41
-`redundancyFactor`: The number of data copies in each backend chain. This subfield is required if the `mode` field is set to `distributed`.
41
42
-`partitions`: The number of partitions to deploy. This subfield is required if the `mode` field is set to `distributed`.
42
-
-`workers`: The number of workers to deploy, currently it must be set to `1`. This subfield is required if the `mode` field is set to `distributed`.
43
+
-`workers`: The number of workers to deploy per backend, currently it must be set to `1`. This subfield is required if the `mode` field is set to `distributed`.
0 commit comments