You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jason Gustafson (Jira)" <ji...@apache.org> on 2020/09/17 16:48:00 UTC
[jira] [Created] (KAFKA-10498) Consumer should do offset/epoch
validation through `Fetch` when possible
Jason Gustafson created KAFKA-10498:
---------------------------------------
Summary: Consumer should do offset/epoch validation through `Fetch` when possible
Key: KAFKA-10498
URL: https://issues.apache.org/jira/browse/KAFKA-10498
Project: Kafka
Issue Type: Improvement
Reporter: Jason Gustafson
Assignee: Chia-Ping Tsai
Currently the consumer has logic to detect truncations (as a result of unclean leader election for example) using the OffsetsForLeaderEpoch API. It is a rather cumbersome and expensive process since we have to check for the need to send this request on every poll(). We should be able to do better now that KIP-595 has built support for truncation detection directly into the `Fetch` protocol. This should allow us to skip validation when we know that the `Fetch` version is high enough.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)