Thanks Dong, I made a pass over the wiki and it lgtm. Just a quick question: can we completely eliminate the OffsetOutOfRangeException with this approach? Say if there is consecutive leader changes such that the cached metadata's partition epoch is 1, and the metadata fetch response returns with partition epoch 2 pointing to leader broker A, while the actual up-to-date metadata has partition epoch 3 whose leader is now broker B, the metadata refresh will still succeed and the follow-up fetch request may still see OORE?
Guozhang On Tue, Jan 23, 2018 at 3:47 PM, Dong Lin <lindon...@gmail.com> wrote: > Hi all, > > I would like to start the voting process for KIP-232: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > 232%3A+Detect+outdated+metadata+using+leaderEpoch+and+partitionEpoch > > The KIP will help fix a concurrency issue in Kafka which currently can > cause message loss or message duplication in consumer. > > Regards, > Dong > -- -- Guozhang
