Kafka: adding partitions breaks key ordering permanently

The default partitioner is murmur2(key) % partitionCount. Change the count and existing keys hash somewhere new - so a key's history is split across two partitions and its ordering guarantee is gone for good.

• Kafka: linger.ms=0 does not mean every record is sent alone
• Kafka: an eager rebalance stops the entire consumer group
• Kafka: log compaction never removes the last record for a key, including a tombstone
• Kafka: consumer lag on one partition is skew, not a scaling problem
• Kafka: a read_committed consumer stalls behind one open transaction
• Kafka: a non-idempotent producer reorders on retry

---

Run this yourself in the Online Java Compiler, spin up a live REST API in the API Sandbox, or practise with Java interview questions.

Published 2026-08-25

© Java Coding Hub · About · Contact · Privacy · Terms