When p99 produce latency jumps, the leadership distribution is the first place to look

Redpanda's per-partition Raft groups make latency sensitive to how partition leadership is distributed. When leaders concentrate on a subset of brokers, those nodes saturate while the rest of the cluster is idle, and tail latency rises well before average latency shows anything. AceMQ diagnoses and rebalances.

Redpanda clusters on Kubernetes or cloud instances with local NVMe or network-attached storage, serving latency-sensitive producers.

AceMQ correlates per-broker leadership counts, disk write latency, and CPU throttling metrics against the latency percentiles to identify which layer is actually saturated. Leadership is rebalanced and partition assignment corrected first, then storage class and resource limits are addressed where the hardware is genuinely the constraint.

• 1
  Per-broker Raft leadership count and partition distribution analysis correlated with produce latency percentiles
• 2
  Leadership rebalancing and partition reassignment to spread write load evenly across the cluster
• 3
  Disk write latency and sustained throughput validation against the storage class actually provisioned
• 4
  Kubernetes CPU limit and reactor thread review to eliminate throttling of the seastar shard threads
• 5
  Partition count review for topics whose parallelism is too low for their throughput regardless of leadership placement
• 6
  Producer batching, linger, and acknowledgment settings tuned against the durability requirement rather than defaults