I concur with what Peter mentioned. You should wait for the
under-replicated partition count to be zero.
The increase in latency could be expected. Let's try to take a deeper look
at what happens during a rolling restart.
When you perform a controlled shutdown of a node, it will tell the
controll
When doing rolling restarts, I always wait until the under-replicated partition
count returns to zero before restarting the next broker. This state is achieved
AFTER the last restarted broker returns to a running state. If you just wait
for the running state, you risk restarting the next broker
Hello,
I'm doing some tests with rolling restarts in a Kafka cluster and I have a
couple of questions related to the impact of rolling restarts on Kafka
consumers/producers and on the overall process.
First, some context on my setup:
- Kafka cluster with 3 nodes.
- Topic replication factor
Hello,
I'm doing some tests with rolling restarts in a Kafka cluster and I have a
couple of questions related to the impact of rolling restarts on Kafka
consumers/producers and on the overall process.
First, some context on my setup:
- Kafka cluster with 3 nodes.
- Topic replication factor