You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Status

Current state: "Under Discussion"

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

JIRA: here 

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

Motivation

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.

Compatibility, Deprecation, and Migration Plan

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

None

  • No labels