KIP-903 — Replicas with stale broker epoch should not be allowed to join the ISR
Accepted Kafka 3.5 BrokerKRaft
Enforces in KRaft mode that an AlterPartition request is rejected (INELIGIBLE_REPLICA) if any proposed ISR member has a broker epoch older than the epoch tracked by the leader at the time of the Fetch request. A race where a broker reboots with a new empty disk, gets re-registered, and is then added to the ISR by a stale AlterPartition from before the fence was lifted could allow that broker to become leader with an empty log, causing data loss.
Protocol Impact
Fetch v15 · AlterPartition v3
Details
| Author | Calvin Liu |
| Status | Accepted |
| Kafka Version | 3.5 |
| JIRA | KAFKA-14139 |
| Wiki | View on Apache Wiki |
| Created | 2023-01-12 |
| Last Modified | 2023-03-17 |
Explore how this KIP affects the Kafka protocol in the Protocol Explorer, or see the full KIP database.