@@ -144,11 +144,11 @@ Changes to the Kubernetes controller configuration can then be deployed using
144
144
Control] [ using version control ] .
145
145
146
146
:::{CAUTION}
147
- If ` discovery.zen.minimum_master_nodes ` is set to more than the current
147
+ If [ discovery.zen.minimum_master_nodes] is set to more than the current
148
148
number of nodes in the cluster, the cluster will disband. On the other
149
149
hand, a number that is too small might lead to a [ split-brain] scenario.
150
150
151
- Accordingly, it is important to [ adjust this number carefully] when
151
+ Accordingly, it is important to adjust this number carefully when
152
152
scaling CrateDB.
153
153
:::
154
154
@@ -185,11 +185,10 @@ However, you should only do this on a production cluster if you need to
185
185
scale to handle a load spike quickly.
186
186
:::
187
187
188
- [ adjust this number carefully ] : https://cratedb.com/docs/crate/reference/en/3.3/config/cluster.html#discovery-zen-minimum-master-nodes
189
188
[ containerization ] : https://www.docker.com/resources/what-container
190
189
[ cratedb docker image ] : https://hub.docker.com/_/crate/
191
190
[ deleted and recreated ] : https://kubernetes.io/docs/concepts/cluster-administration/manage-deployment/#disruptive-updates
192
- [ discovery.zen.minimum_master_nodes ] : https://cratedb .com/docs /crate/reference/en/ 3.3/config/cluster.html #discovery-zen-minimum-master-nodes
191
+ [ discovery.zen.minimum_master_nodes ] : https://github .com/crate /crate/blob/ 3.3/blackbox/docs/ config/cluster.rst #discovery
193
192
[ docker ] : https://www.docker.com/
194
193
[ gateway.expected_data_nodes ] : https://cratedb.com/docs/crate/reference/en/latest/admin/system-information.html#recovery-expected-data-nodes
195
194
[ gateway.recover_after_data_nodes ] : https://cratedb.com/docs/crate/reference/en/latest/admin/system-information.html#recovery-after-data-nodes
0 commit comments