[ https://issues.apache.org/jira/browse/KAFKA-8001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stanislav Kozlovski updated KAFKA-8001: --------------------------------------- Summary: AlterLogDirs: Fetch from future replica stalls when local replica becomes a leader (was: Fetch from future replica stalls when local replica becomes a leader) > AlterLogDirs: 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.0, 2.1.1 > Reporter: Anna Povzner > Assignee: Vikas Singh > Priority: Critical > > 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. > This is a burden operationally, because log dir movement > 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 (v8.3.4#803005)