This page is meant as a template for writing a KIP. To create a KIP choose Tools->Copy on this page and modify with your content and replace the heading with the next KIP number and a description of your issue. Replace anything in italics with your own description.

Status

Current state:   [One of "Under Discussion", "Accepted", "Rejected"]

Discussion thread: here [Change the link from the KIP proposal email archive to your own email thread]

JIRA: here [Change the link from KAFKA-1 to your own ticket] 

Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).

Motivation

Describe the problems you are trying to solve.

Public Interfaces

Briefly list any new interfaces that will be introduced as part of this proposal or any existing interfaces that will be removed or changed. The purpose of this section is to concisely call out the public contract that will come along with this feature.

A public interface is any change to the following:

• Binary log format

• The network protocol and api behavior

• Any class in the public packages under clientsConfiguration, especially client configuration

  • org/apache/kafka/common/serialization

  • org/apache/kafka/common

  • org/apache/kafka/common/errors

  • org/apache/kafka/clients/producer

  • org/apache/kafka/clients/consumer (eventually, once stable)

• Monitoring

• Command line tools and arguments

• Anything else that will likely break existing users in some way when they upgrade

Proposed Changes

There are no official tools available to measure the performance of aborted transactions. The ProducerPerformance tool currently supports transactional producers but lacks the ability to randomly abort transactions during testing. This limitation prevents users from properly evaluating how transactional producers behave when transactions are aborted, which is important for production systems where transaction failures can occur.

The ability to test aborted transactions is crucial for:

1. Understanding the overhead associated with transaction abortion;
2. Evaluating the performance impact of failed transactions on producer throughput;
3. Validating transaction recovery mechanisms;
4. Benchmarking transactional producers under realistic failure scenarios.

Public Interfaces

New Configuration Option:
    --transaction-abort-ratio: Ratio of transactions to abort (0.0 to 1.0). Default is 0.0 (no aborts). 

• Default value: 0.0 (no transactions aborted);
• When set to 1.0, all transactions will be aborted;
• When set to 0.5, half of the transactions will be aborted;

Proposed Changes

This feature will add a new configuration option to the ProducerPerformance tool that allows users to specify a ratio of transactions to abort during testing. This will enable users to simulate transaction failure scenarios while measuring performance metrics.Describe the new thing you want to do in appropriate detail. This may be fairly extensive and have large subsections of its own. Or it may be a few sentences. Use judgement based on the scope of the change.

Compatibility, Deprecation, and Migration Plan

• What impact (if any) will there be on existing users?
• If we are changing behavior how will we phase out the older behavior?
• If we need special migration tools, describe them here.
• When will we remove the existing behavior?

Test Plan

Describe in few sentences how the KIP will be tested. We are mostly interested in system tests (since unit-tests are specific to implementation details). How will we know that the implementation works as expected? How will we know nothing broke?

Rejected Alternatives

This feature is fully backward compatible:

• When --transaction-abort-ratio is not specified, the tool behaves exactly as before;
• No existing configuration options are changed or removed;
• All existing functionality remains intact.

Test Plan

The patch will include unit tests to ensure full coverage:

• Test command-line argument parsing;
• Verify abort ratio validation;
• Test random abortion logic with different ratios.

Rejected Alternatives

NoneIf there are alternative ways of accomplishing the same thing, what were they? The purpose of this section is to motivate why the design is the way it is and not some other way.