Transaction Abort Rate Signals Coordination or Timeout Issues
warningHigh pulsar_transaction_aborted_count relative to pulsar_transaction_active indicates transactions are failing to commit, potentially due to coordinator failures, network issues, or application-side timeout problems.
Monitor pulsar_transaction_aborted_count for sustained increases. Compare with pulsar_transaction_active to assess abort rate. Check pulsar_transaction_append_log_count for transaction log persistence issues. Correlate with metadata store latency metrics to identify coordinator bottlenecks.
Investigate transaction coordinator health and ensure coordinators are not overloaded. Review transaction timeout configurations and adjust if legitimate processing requires longer durations. Check for network issues between clients and transaction coordinators. Verify BookKeeper capacity for transaction log storage. Monitor application logs for transactional API usage errors.