Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(node pools): impact on racks when moving nodes #9894

Merged
merged 1 commit into from
Mar 29, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions documentation/assemblies/configuring/assembly-config.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -66,6 +66,7 @@ include::../../modules/configuring/proc-manual-delete-pod-pvc-zookeeper.adoc[lev
//configuring node pools
include::../../modules/configuring/con-config-node-pools.adoc[leveloffset=+1]
include::../../modules/configuring/proc-managing-node-pools-ids.adoc[leveloffset=+2]
include::../../modules/configuring/con-node-pools-racks.adoc[leveloffset=+2]
include::../../modules/configuring/proc-scaling-up-node-pools.adoc[leveloffset=+2]
include::../../modules/configuring/proc-scaling-down-node-pools.adoc[leveloffset=+2]
include::../../modules/configuring/proc-moving-node-pools.adoc[leveloffset=+2]
Expand Down
15 changes: 15 additions & 0 deletions documentation/modules/configuring/con-node-pools-racks.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
[id='config-node-pools-dependencies-{context}']
= Impact on racks when moving nodes from node pools

[role="_abstract"]
If rack awareness is enabled on a Kafka cluster, replicas can be spread across different racks, data centers, or availability zones.
When moving nodes from node pools, consider the implications on the cluster topology, particularly regarding rack awareness.
Removing specific pods from node pools, especially out of order, may break the cluster topology or cause an imbalance in distribution across racks.
An imbalance can impact both the distribution of nodes themselves and the partition replicas within the cluster.
An uneven distribution of nodes and partitions across racks can affect the performance and resilience of the Kafka cluster.

Plan the removal of nodes strategically to maintain the required balance and resilience across racks.
Use the `strimzi.io/remove-node-ids` annotation to move nodes with specific IDs with caution.
Ensure that configuration to spread partition replicas across racks and for clients to consume from the closest replicas is not broken.

TIP: Use Cruise Control and the `KafkaRebalance` resource with the `RackAwareGoal` to make sure that replicas remain distributed across different racks.
Loading