Produce (Records / S)

You can check the behaviour of your consumer under various types of messages
You can artificially create lags for your topic by producing messages at a high throughput

Parameters

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
Records per seconds	The number of records per second. Should be between 1 and 10.
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

Useful Templates

See all

Simulate Kafka brokers downtime and see how consumers are handling topic lag

An experiment to block access to brokers for consumers while producing records in the topic. The consumers should get back to consume when the kafka brokers are available again and the accumulated lag must be deal with quickly.

Message Queue

Kafka

Recoverability

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