Steadybit

Check the partition activity for a given topic (leader election, replicas going offline or in-sync, new replica order).

Produce records periodically (records per second).

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

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.


## Intent

Intentionally deny access to the topic for consumers and during this time where consumption is stopped, delete records.

We can check the logs of the consumers to see how they handle the loss of records and also authorization access issues.

Parameter	Description	Default
Record Key	Optional. You can define a key, that could define the partitions used based on the partitions logics in place (default is round robin).
Record Value	Required. The value of the record to generate
Record Headers	The Record Headers.
Duration	The duration of the attack.	10s
Number of records	The number of records to create, the rate will be defined by this number divided by the duration of the attack.
Success Rate	How many percent of the records must be at least successful, that means not encountering any errors while sending the record to the broker.	100%
MaxConcurrent	Maximum count on parallel running requests. (min 1, max 10)	5

Produce (# of Records)

Produce (# of Records)

Produce (# of Records)

Produce (# of Records)

Introduction

Use Cases

Parameters

Check Kafka consumer's reaction to record loss

Intent

Check Partitions

Produce (Records / s)

Reduce Message Batch Size

Trigger Delete Records

Trigger Partition Leader Election