blob: efe1d81f939da13ade49a089ca70b51bb961f853 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
|
## Re-assign Leadership
This is one of the cases where this repo begs to differ from traditional Kafka setups.
In Kubernetes the restart of a pod, and subsequent start on a different node, should be a non-event.
> ”when a broker is stopped and restarted, it does not resume leadership of any partitions automatically”
_-- Neha Narkhede, Gwen Shapira, and Todd Palino. ”Kafka: The Definitive Guide”_
Create the `preferred-replica-election-job.yml` resource, after deleting any previous one.
## Change a Partition's Replicas
> ”From time to time, it may be necessary to change the replica assignments for a partition. Some examples of when this might be needed are:
> * If a topic’s partitions are not balanced across the cluster, causing uneven load on brokers
> * If a broker is taken offline and the partition is under-replicated
> * If a new broker is added and needs to receive a share of the cluster load”
_-- Neha Narkhede, Gwen Shapira, and Todd Palino. ”Kafka: The Definitive Guide”_
Use the `reassign-paritions-job.yml`, after editing `TOPICS` and `BROKERS`.
|
