Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Today during leader failover we will have a weakness period when the followers truncate their data before fetching from the new leader, i.e., number of in-sync replicas is just 1. If during this time the leader has also failed then produce requests with ack >1 that have get responded will still be lost. To avoid this scenario we would prefer to hold the produce request in purgatory until replica's HW has larger than the offset instead of just their end-of-log offsets.
Attachments
Issue Links
- is blocked by
-
KAFKA-1188 Stale LeaderAndIsr request could be handled by the broker on Controller failover
- Resolved
- is related to
-
KAFKA-3919 Broker faills to start after ungraceful shutdown due to non-monotonically incrementing offsets in logs
- Resolved
- mentioned in
-
Page Loading...