[ 
https://issues.apache.org/jira/browse/KAFKA-8102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16800881#comment-16800881
 ] 

ASF GitHub Bot commented on KAFKA-8102:
---------------------------------------

cmccabe commented on pull request #6444: KAFKA-8102: Add an interval-based 
Trogdor transaction generator
URL: https://github.com/apache/kafka/pull/6444
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Trogdor - Add Produce workload transaction generator by interval
> ----------------------------------------------------------------
>
>                 Key: KAFKA-8102
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8102
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Stanislav Kozlovski
>            Assignee: Stanislav Kozlovski
>            Priority: Major
>
> Trogdor's specification for produce worker workloads 
> ([ProduceBenchSpec|https://github.com/apache/kafka/blob/trunk/tools/src/main/java/org/apache/kafka/trogdor/workload/ProduceBenchSpec.java])
>  supports configuring a transactional producer using a class that implements 
> `TransactionGenerator` interface.
>  
> [UniformTransactioGenerator|https://github.com/apache/kafka/blob/trunk/tools/src/main/java/org/apache/kafka/trogdor/workload/UniformTransactionsGenerator.java]
>  which triggers a transaction every N records.
> It would be useful to have a generator which supports triggering a 
> transaction in an interval - e.g every 100 milliseconds. This is how Kafka 
> Streams configures its own [EOS semantics by 
> default|https://github.com/apache/kafka/blob/8e975400711b0ea64bf4a00c8c551e448ab48416/streams/src/main/java/org/apache/kafka/streams/StreamsConfig.java#L140].



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to