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

Posted to dev@kafka.apache.org by "Anna Povzner (JIRA)" <ji...@apache.org> on 2019/02/26 00:51:00 UTC

[jira] [Created] (KAFKA-8001) Fetch from future replica stalls when local replica becomes a leader

Anna Povzner created KAFKA-8001:
-----------------------------------

             Summary: Fetch from future replica stalls when local replica becomes a leader
                 Key: KAFKA-8001
                 URL: https://issues.apache.org/jira/browse/KAFKA-8001
             Project: Kafka
          Issue Type: Bug
          Components: core
    Affects Versions: 2.1.1
            Reporter: Anna Povzner


With KIP-320, fetch from follower / future replica returns FENCED_LEADER_EPOCH if current leader epoch in the request is lower than the leader epoch known to the leader (or local replica in case of future replica fetching). In case of future replica fetching from the local replica, if local replica becomes the leader of the partition, the next fetch from future replica fails with FENCED_LEADER_EPOCH and fetching from future replica is stopped until the next leader change. 

Proposed solution: on local replica leader change, future replica should "become a follower" again, and go through the truncation phase. Or we could optimize it, and just update partition state of the future replica to reflect the updated current leader epoch. 



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