You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2018/07/02 14:40:00 UTC

[jira] [Assigned] (KAFKA-6859) Follower should not send OffsetForLeaderEpoch for undefined leader epochs

     [ https://issues.apache.org/jira/browse/KAFKA-6859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ismael Juma reassigned KAFKA-6859:
----------------------------------

    Assignee: Stanislav Kozlovski

> Follower should not send OffsetForLeaderEpoch for undefined leader epochs
> -------------------------------------------------------------------------
>
>                 Key: KAFKA-6859
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6859
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.11.0.0
>            Reporter: Anna Povzner
>            Assignee: Stanislav Kozlovski
>            Priority: Major
>             Fix For: 2.1.0
>
>
> This is more of an optimization, rather than correctness.
> Currently, if the follower on inter broker protocol version 0.11 and higher, but on older message format, it does not track leader epochs. However, will still send OffsetForLeaderEpoch request to the leader with undefined epoch which is guaranteed to return undefined offset, so that the follower truncated to high watermark. Another example is a bootstrapping follower that does not have any leader epochs recorded, 
> It is cleaner and more efficient to not send OffsetForLeaderEpoch requests to the follower with undefined leader epochs, since we already know the answer.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)