Re: [PR] KAFKA-20961: Carry leader epoch history over when replacing the current log with the future log [kafka]

["haung921209 (via GitHub)" <gi...@apache.org>]

haung921209 commented on PR #23205:
URL: https://github.com/apache/kafka/pull/23205#issuecomment-5579371503

   @hudeqi @mimaison could one of you take a look when you have a chance?
   
   This is the same defect as KAFKA-15608 (#14553 was the earlier attempt): when `LogManager` replaces the current log with the future log, the leader epoch cache is not carried over, so an epoch with no records behind it is lost and the leader ends up throwing `OffsetOutOfRangeException` in a loop on an idle partition. What's different from #14553 is a deterministic unit-level reproduction on trunk (three tests that fail before the fix) and carrying the full epoch history rather than only the latest entry.
   
   I don't have Jira permissions yet to assign KAFKA-20961 to myself — if someone could add me to the contributors list I'd appreciate it.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: jira-unsubscribe@kafka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org