Restart Confluent Platform¶
There are cases when it is necessary to trigger a restart of a Confluent Platform cluster, such as to apply a license change or to apply credentials changes in a Kubernetes Secret.
Rolling restart of Kafka¶
Some changes in Kafka CR properties require Kafka pods to restart. The rolling restart process of Kafka is different from that of other Confluent components because the integrity of the Kafka data must be preserved during the restart.
CFK restarts one broker at a time, starting with the highest numbered broker to 0, i.e., broker-n to broker-0, and checks that there are no under replicated partitions on the broker before proceeding to the next broker. The active controller is not in consideration in this process.
Restart Confluent Platform components¶
The following are examples of when you need to restart Confluent Platform components:
- Changing Telemetry settings
- Loading credentials
- Updating the license
- Updating the external load balancer domain name
- Updating the component prefix
- Updating the authentication user list
To restart a Confluent Platform component cluster:
Find the name of the StatefulSet corresponding to the Confluent Platform cluster you want to restart:
kubectl get statefulset --namespace <namespace>
Using the StatefulSet name,
<name-of-statefulset>, from the previous step, roll the cluster:
kubectl rollout restart statefulset/<name-of-statefulset> --namespace <namespace>