From d115cdd2b8341bc71372c388845e5c62ffe15b53 Mon Sep 17 00:00:00 2001 From: Nick Larsen Date: Thu, 1 Aug 2024 13:43:23 +0200 Subject: [PATCH] docs: remove home module from refs (stackabletech/documentation#637) --- docs/modules/zookeeper/pages/usage_guide/log_aggregation.adoc | 2 +- .../zookeeper/pages/usage_guide/resource_configuration.adoc | 2 +- .../pages/usage_guide/using_multiple_role_groups.adoc | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/modules/zookeeper/pages/usage_guide/log_aggregation.adoc b/docs/modules/zookeeper/pages/usage_guide/log_aggregation.adoc index deb01b05..9f3d297b 100644 --- a/docs/modules/zookeeper/pages/usage_guide/log_aggregation.adoc +++ b/docs/modules/zookeeper/pages/usage_guide/log_aggregation.adoc @@ -28,4 +28,4 @@ spec: ---- Further information on how to configure logging, can be found in -xref:home:concepts:logging.adoc[]. +xref:concepts:logging.adoc[]. diff --git a/docs/modules/zookeeper/pages/usage_guide/resource_configuration.adoc b/docs/modules/zookeeper/pages/usage_guide/resource_configuration.adoc index 91f462c4..522d1e93 100644 --- a/docs/modules/zookeeper/pages/usage_guide/resource_configuration.adoc +++ b/docs/modules/zookeeper/pages/usage_guide/resource_configuration.adoc @@ -20,7 +20,7 @@ In the above example, all ZooKeeper nodes in the default group will store data ( == Resource requests -include::home:concepts:stackable_resource_requests.adoc[] +include::concepts:stackable_resource_requests.adoc[] A minimal HA setup consisting of 3 ZooKeeper instances has the following https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/[resource requirements]: diff --git a/docs/modules/zookeeper/pages/usage_guide/using_multiple_role_groups.adoc b/docs/modules/zookeeper/pages/usage_guide/using_multiple_role_groups.adoc index e6dd99d1..82a8805e 100644 --- a/docs/modules/zookeeper/pages/usage_guide/using_multiple_role_groups.adoc +++ b/docs/modules/zookeeper/pages/usage_guide/using_multiple_role_groups.adoc @@ -1,7 +1,7 @@ = Using multiple role groups // abstract/summary -ZooKeeper uses a unique ID called _myid_ to identify each server in the cluster. The Stackable Operator for Apache ZooKeeper assigns the _myid_ to each Pod from the https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#ordinal-index[ordinal index] given to the Pod by Kubernetes. This index is unique over the Pods in the StatefulSet of the xref:home:concepts:roles-and-role-groups.adoc[role group]. +ZooKeeper uses a unique ID called _myid_ to identify each server in the cluster. The Stackable Operator for Apache ZooKeeper assigns the _myid_ to each Pod from the https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#ordinal-index[ordinal index] given to the Pod by Kubernetes. This index is unique over the Pods in the StatefulSet of the xref:concepts:roles-and-role-groups.adoc[role group]. When using multiple role groups in a cluster, this will lead to different ZooKeeper Pods using the same _myid_. Each role group is represented by its own StatefulSet, and therefore always identified starting with `0`. @@ -29,4 +29,4 @@ spec: <1> The `myidOffset` property set to 10 for the secondary role group -The `secondary` role group _myid_ starts from id `10`. The `primary` role group will start from `0`. This means, the replicas of the role group `primary` should not be scaled higher than `10` which results in `10` `primary` Pods using a _myid_ from `0` to `9`, followed by the `secondary` Pods starting at _myid_ `10`. \ No newline at end of file +The `secondary` role group _myid_ starts from id `10`. The `primary` role group will start from `0`. This means, the replicas of the role group `primary` should not be scaled higher than `10` which results in `10` `primary` Pods using a _myid_ from `0` to `9`, followed by the `secondary` Pods starting at _myid_ `10`.