Start Free Trial

Trigger Partition Leader Election

Attack

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.

Targets:

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

Targets:

Trigger Partition Leader Election

Attack

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.

Targets:

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

Targets:

Go back to list

The action "Trigger Partition Leader Election" within the experiment editor.

The action "Trigger Partition Leader Election" within the experiment editor.

Introduction

With this action, Steadybit elects the preferred replica for a partition.

Use Cases

Start the election of a new leader choosing the preferred replica for a partition, can be useful to trigger the election before the imbalance threshold.

Parameters

Parameter	Description	Default
Partition to elect new leader"	One or more partitions to trigger a new leader election

Useful Templates

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.

More Kafka Topic Actions

Check Partitions

Check the partition activity for a given topic

Produce (# of Records)

Produce a certain amount of kafka messages for a given duration

Produce (Records / s)

Produce records periodically (records per second)

Reduce Message Batch Size

Change the max bytes per message

Trigger Delete Records

Trigger delete records to move the offset relative to the last known offset for each selected partition

Start Using Steadybit Today

Get started with Steadybit, and you’ll get access to all of our features to discover the full power of Steadybit. Available for SaaS and on-prem!

Are you unsure where to begin?

No worries, our reliability experts are here to help: book a demo with them!

Statistics

-Stars

Tags

Message Queue

Kafka

Homepage

hub.steadybit.com/extension/com.steadybit.extension_kafka

GitHub

steadybit/extension-kafka

ghcr.io

steadybit/extension-kafka

License

MaintainerSteadybit

support@steadybit.com

https://steadybit.com

Start Free Trial

HubActions Targets Advice Extensions Templates

Support & ResourcesDocumentation Youtube Tutorials Case Studies

ContactsAbout us Contact us Imprint and legal Terms of services

© 2025 Steadybit GmbH. All rights reserved.