[转帖]Welcome to the di-kafkameter wiki!
https://github.com/rollno748/di-kafkameter/wiki#producer-elements
Introduction
DI-Kafkameter is a JMeter plugin that allows you to test and measure the performance of Apache Kafka.
Components
The DI-Kafkameter comprises of 2 components, which are
- Producer Component
- Kafka Producer Config
- Kafka Producer Sampler
- Consumer Component
- Kafka Consumer Config
- Kafka Consumer Sampler
Producer Component (Publish a Message to a Topic)
To publish/send a message to a Kafka topic you need to add producer components to the testplan.
- The Kafka Producer config is responsible to hold the connection information, which includes security and other properties required to talk to the broker.
- The Kakfa Producer Sampler helps to send messages to the topic with the connection established using Config element.

Right click on Test Plan -> Add -> Config Element -> Kafka Producer Config
Provide a Variable name to export the connection object (Which will be used in Sampler element)
Provide the Kafka connection configs (list of Brokers with comma separated)
Provide a Client ID (Make it unique, to define where you sending the message from)
Select the right security to connect to brokers (This will be completely based on how Kafka security is defined)
For JAAS Security, You need to add the below key and value to the Additional Properties
Config key: sasl.jaas.config
Config value: org.apache.kafka.common.security.scram.ScramLoginModule required username="<USERNAME>" password="<PASSWORD>";

Right click on Test Plan -> Add -> Sampler -> Kafka Producer Sampler
Use the same Variable name which was defined in the config element
Define the topic name where you want to send the message (Case sensitive)
Kafka Message - The Original message which needs to be pushed to the topic
Partition String (Optional) - This option helps you to post messages to particular partition by providing the partition number
Message Headers (Optional) - This helps in adding headers to the messages which are being pushed (Supports more than one header)
Consumer Component (Read Message from a topic)
To Consume/Read a message from a Kafka topic you need to add Consumer components to the testplan.
- The Kafka Consumer config is responsible to hold the connection information, which includes security and other properties required to talk to the broker.
- The Kafka Consumer Sampler helps to read messages from the topic with the connection established using Config element.

Right click on Test Plan -> Add -> Config Element -> Kafka Consumer Config
Provide a Variable name to export the connection object (Which will be used in Sampler element)
Provide the Kafka connection configs (list of Brokers with comma separated)
Provide a Group ID (Make it unique, to define the group your consumer belongs to)
Define the topic name where you want to send the message (Case sensitive)
No Of Messages to Poll - This allows you to define the number of messages to read within a request (Defaults to 1)
Select the right security to connect to brokers (This will be completely based on how Kafka security is defined)
Auto Commit - This will set the offset as read, once the message is consumed
Select the right security to connect to brokers (This will be completely based on how Kafka security is defined)
For JAAS Security, You need to add the below key and value to the Additional Properties
Config key: sasl.jaas.config
Config value: org.apache.kafka.common.security.scram.ScramLoginModule required username="<USERNAME>" password="<PASSWORD>";

Right click on Test Plan -> Add -> Sampler -> Kafka Consumer Sampler
Use the same Variable name which was defined in the config element
Poll timeout - This helps to set the polling timeout for consumer to read from topic (Defaults to 100 ms)
Commit Type - Defines the Commit type (Sync/Async)
Producer Properties
Supported Producer properties which can be added to Additional Properties field.
| Property | Available Options | Default |
|---|---|---|
| acks | [0, 1, -1] | 1 |
| batch.size | positive integer | 16384 |
| bootstrap.servers | comma-separated host:port pairs | localhost:9092 |
| buffer.memory | positive long | 33554432 |
| client.id | string | "" |
| compression.type | [none, gzip, snappy, lz4, zstd] | none |
| connections.max.idle.ms | positive long | 540000 |
| delivery.timeout.ms | positive long | 120000 |
| enable.idempotence | [true, false] | false |
| interceptor.classes | fully-qualified class names | [] |
| key.serializer | fully-qualified class name | org.apache.kafka.common.serialization.StringSerializer |
| linger.ms | non-negative integer | 0 |
| max.block.ms | non-negative long | 60000 |
| max.in.flight.requests.per.connection | positive integer | 5 |
| max.request.size | positive integer | 1048576 |
| metadata.fetch.timeout.ms | positive long | 60000 |
| metadata.max.age.ms | positive long | 300000 |
| partitioner.class | fully-qualified class name | org.apache.kafka.clients.producer.internals.DefaultPartitioner |
| receive.buffer.bytes | positive integer | 32768 |
| reconnect.backoff.ms | non-negative long | 50 |
| request.timeout.ms | positive integer | 30000 |
| retries | non-negative integer | 0 |
| sasl.jaas.config | string | null |
| sasl.kerberos.kinit.cmd | string | /usr/bin/kinit |
| sasl.kerberos.min.time.before.relogin | positive long | 60000 |
| sasl.kerberos.service.name | string | null |
| sasl.mechanism | [GSSAPI, PLAIN, SCRAM-SHA-256, SCRAM-SHA-512] | GSSAPI |
| security.protocol | [PLAINTEXT, SSL, SASL_PLAINTEXT, SASL_SSL] | PLAINTEXT |
| sender.flush.timeout.ms | non-negative long | 0 |
| send.buffer.bytes | positive integer | 131072 |
| value.serializer | fully-qualified class name | org.apache.kafka.common.serialization.StringSerializer |
Consumer Properties
Supported Consumer properties which can be added to Additional Properties field.
| Property | Available Options | Default |
|---|---|---|
| auto.commit.interval.ms | positive integer | 5000 |
| auto.offset.reset | [earliest, latest, none] | latest |
| bootstrap.servers | comma-separated host:port pairs | localhost:9092 |
| check.crcs | [true, false] | true |
| client.id | string | "" |
| connections.max.idle.ms | positive long | 540000 |
| enable.auto.commit | [true, false] | true |
| exclude.internal.topics | [true, false] | true |
| fetch.max.bytes | positive long | 52428800 |
| fetch.max.wait.ms | non-negative integer | 500 |
| fetch.min.bytes | non-negative integer | 1 |
| group.id | string | "" |
| heartbeat.interval.ms | positive integer | 3000 |
| interceptor.classes | fully-qualified class names | [] |
| isolation.level | [read_uncommitted, read_committed] | read_uncommitted |
| key.deserializer | fully-qualified class name | org.apache.kafka.common.serialization.StringDeserializer |
| max.partition.fetch.bytes | positive integer | 1048576 |
| max.poll.interval.ms | positive long | 300000 |
| max.poll.records | positive integer | 500 |
| metadata.max.age.ms | positive long | 300000 |
| metadata.fetch.timeout.ms | positive long | 60000 |
| receive.buffer.bytes | positive integer | 32768 |
| reconnect.backoff.ms | non-negative long | 50 |
| request.timeout.ms | positive integer | 30000 |
| retry.backoff.ms | non-negative long | 100 |
| sasl.jaas.config | string | null |
| sasl.kerberos.kinit.cmd | string | /usr/bin/kinit |
| sasl.kerberos.min.time.before.relogin | positive long | 60000 |
| sasl.kerberos.service.name | string | null |
| sasl.mechanism | [GSSAPI, PLAIN, SCRAM-SHA-256, SCRAM-SHA-512] | GSSAPI |
| security.protocol | [PLAINTEXT, SSL, SASL_PLAINTEXT, SASL_SSL] | PLAINTEXT |
| send.buffer.bytes | positive integer | 131072 |
| session.timeout.ms | positive integer | 10000 |
| value.deserializer | fully-qualified class name | org.apache.kafka.common.serialization.StringDeserializer |
[转帖]Welcome to the di-kafkameter wiki!的更多相关文章
- 用Zim替代org-mode?
三年前我玩过Zim,当时还写了一篇<Zim - 普通人的Org-mode>,当时还说我还是会坚持使用emacs org-mode.但最近我又在考虑是不是回头用Zim来写博客文章.整理知识库 ...
- jmeter取样器之KafkaProducerSampler(往kafka插入数据)
项目背景 性能测试场景中有一个业务场景的数据抽取策略是直接使用kafka队列,该场景需要准备的测试数据是kafka队列里的数据,故需要实现插入数据到kafka队列,且需要实现控制每分钟插入多少条数据. ...
- 【好文转帖】控制反转(IOC)和依赖注入(DI)的区别
IOC inversion of control 控制反转 DI Dependency Injection 依赖注入 要理解这两个概念,首先要搞清楚以下几个问题: 参与者都有谁? 依赖:谁 ...
- [转帖]什么是IOC(控制反转)、DI(依赖注入)
什么是IOC(控制反转).DI(依赖注入) 2018-08-22 21:29:13 Ming339456 阅读数 20642 原文地址(摘要了部分内容):https://blog.csdn.net ...
- Ninject之旅之一:理解DI
摘要: DI(IoC)是当前软件架构设计中比较时髦的技术.DI(IoC)可以使代码耦合性更低,更容易维护,更容易测试.现在有很多开源的依赖反转的框架,Ninject是其中一个轻量级开源的.net DI ...
- [Android分享] 【转帖】Android ListView的A-Z字母排序和过滤搜索功能
感谢eoe社区的分享 最近看关于Android实现ListView的功能问题,一直都是小伙伴们关心探讨的Android开发问题之一,今天看到有关ListView实现A-Z字母排序和过滤搜索功能 ...
- MVC 5 + EF6 完整教程15 -- 使用DI进行解耦
如果大家研究一些开源项目,会发现无处不在的DI(Dependency Injection依赖注入). 本篇文章将会详细讲述如何在MVC中使用Ninject实现DI 文章提纲 场景描述 & 问题 ...
- [转帖][分享] 关于系统DIY--by 原罪
http://wuyou.net/forum.php?mod=viewthread&tid=399277&extra=page%3D1 前几天我发了一个帖子<Windows组件w ...
- AngularJs学习笔记--Dependency Injection(DI,依赖注入)
原版地址:http://code.angularjs.org/1.0.2/docs/guide/di 一.Dependency Injection(依赖注入) 依赖注入(DI)是一个软件设计模式,处理 ...
- 原创:Javascript DI!Angular依赖注入的实现原理
DI是Angular的特色功能,而在Angular 2.0的计划中,DI将成为一个独立的模块,参见 https://github.com/angular/di.js 这意味着它也有机会被用于nodej ...
随机推荐
- 拓扑排序软件设计——ToplogicalSort_app(含有源码、需求分析、可行性分析、概要设计、用户使用手册)
@ 目录 前言 1. 需求分析 2. 可行性分析 2.1 简介 2.2 技术可行性分析 2.2.1 技术实现方案 2.2.2 开发人员技能要求 2.2.3 可行性 2.3 操作可行性分析 2.4 结论 ...
- 【scikit-learn基础】--『监督学习』之 均值聚类
聚类算法属于无监督学习,其中最常见的是均值聚类,scikit-learn中,有两种常用的均值聚类算法:一种是有名的K-means(也就是K-均值)聚类算法,这个算法几乎是学习聚类必会提到的算法:另一个 ...
- GDAL数据集写入空间坐标参考
目录 1. 概述 2. 栅格数据 3. 矢量数据 1. 概述 可以通过GDAL给地理数据写入空间参考信息,不过要注意的是GDAL给矢量数据和栅格数据写入空间坐标参考的接口不太一样. 2. 栅格数据 实 ...
- html2pdf
nodejs 生成pdf比较靠谱,使用chrome核心渲染: puppeteer / phantom 爬虫都好用 good
- 一文带你了解GaussDB(DWS) 的Roach逻辑备份实现原理
摘要:Roach工具是GaussDB(DWS)推出的一款主力的备份恢复工具,包含物理与逻辑备份两种主要能力,本文着重于讲解Roach逻辑备份的实现原理. 一.简介 在大数据时代,数据的完整和可靠性成为 ...
- Python 没有函数重载?如何用装饰器实现函数重载?
摘要:Python 不支持函数重载.当我们定义了多个同名的函数时,后面的函数总是会覆盖前面的函数,因此,在一个命名空间中,每个函数名仅会有一个登记项(entry). 本文分享自华为云社区<为什么 ...
- 利用Appuploader上架IPA步骤
Appuploader可以辅助在Windows.linux或mac系统直接申请iOS证书p12,及上传ipa到App Store.方便在没有苹果电脑情况下上架IPA操作. 一.下载安装iOS上架辅 ...
- Solon2 的 Bean 生命周期
Solon 框架的 Bean 是被容器托管的,所以它的生命周期只限定在容器内部: 时机点 说明 补充 AopContext::new() 是在应用初始化时执行 ::new() AopContext:: ...
- 脑机接口 | 面向步态&神经电生理研究的非人灵长类模型与系统
近期,海南大学生物医学工程学院脑机芯片神经工程团队在Frontiers in Neuroscience期刊上发表了题为<面向步态&神经电生理研究的非人灵长类模型与系统>的学术论文. ...
- xv6book阅读 chapter1
xv6book主要研究了xv6如何实现它的类Unix接口,但是其思想和概念不仅仅适用于Unix.任何操作系统都必须将进程多路复用到底层硬件上,相互隔离进程,并提供受控制的进程间通信机制. 1 了解xv ...