Steadybit logoResilience Hub
Try SteadybitGitHub icon
Steadybit logoResilience Hub

Produce (Records / S)

Attack

Attack

New
Produce records periodically (records per second).
Install now

Produce (Records / S)

Produce records periodically (records per second).
Attack

Attack

Install now

Produce (Records / S)

Attack

Attack

New
Produce records periodically (records per second).
Install now

Produce (Records / S)

Produce records periodically (records per second).
Attack

Attack

Install now
Go back to list
The action "Produce (Records / s)" within the experiment editor.The action "Produce (Records / s)" within the experiment editor.

Introduction

With this action, Steadybit can become a producer and send records at the desired rate.

Use Cases

  • 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

ParameterDescriptionDefault
Record KeyOptional. You can define a key, that could define the partitions used based on the partitions logics in place (default is round robin).
Record ValueRequired. The value of the record to generate
Record HeadersThe Record Headers.
DurationThe duration of the attack.10s
Records per secondsThe number of records per second. Should be between 1 and 10.
Success RateHow many percent of the records must be at least successful, that means not encountering any errors while sending the record to the broker.100%
MaxConcurrentMaximum count on parallel running requests. (min 1, max 10)5
Statistics
-Stars
Tags
Message Queue
Kafka
Homepage
hub.steadybit.com/extension/com.steadybit.extension_kafka
License
MIT
MaintainerSteadybit
Install now

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

Containers

Kafka consumers

Kafka topics

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

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!

Steadybit logoResilience Hub
Try Steadybit
© 2024 Steadybit GmbH. All rights reserved.
Twitter iconLinkedIn iconGitHub icon