Trigger Partition Leader Election
Attack
New
Trigger election for a new leader for a given topic and partition(s), asking for the preferred replica. Warning: in order to force the new election, we change the replica order so that the next in-sync replica is first and the current leader is last.
Trigger Partition Leader Election
Trigger election for a new leader for a given topic and partition(s), asking for the preferred replica. Warning: in order to force the new election, we change the replica order so that the next in-sync replica is first and the current leader is last.Attack
Trigger Partition Leader Election
Attack
New
Trigger election for a new leader for a given topic and partition(s), asking for the preferred replica. Warning: in order to force the new election, we change the replica order so that the next in-sync replica is first and the current leader is last.
Trigger Partition Leader Election
Trigger election for a new leader for a given topic and partition(s), asking for the preferred replica. Warning: in order to force the new election, we change the replica order so that the next in-sync replica is first and the current leader is last.Attack
Go back to list
Validate consumer's behavior when new leader is elected
Verify that your application handles a change of the leader properly.
Motivation
By testing your system's resilience to Kafka leader changes in a partition, you can identify potential weaknesses and take appropriate measures to improve its performance.
Structure
To conduct this experiment, we will ensure that all Kafka topics and producers are ready and that the consumer receives and processes messages correctly. We will then elect a new leader for one partition in Kafka and expect the system to work fine.
Message Queue
Kafka
Recoverability
Kafka consumers
Kafka topics
