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

Posted to jira@kafka.apache.org by "Jason Gustafson (JIRA)" <ji...@apache.org> on 2019/02/26 02:36:00 UTC

[jira] [Updated] (KAFKA-8002) Replica reassignment to new log dir may not complete if future and current replicas segment files have different base offsets

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

Jason Gustafson updated KAFKA-8002:
-----------------------------------
    Priority: Critical  (was: Major)

> Replica reassignment to new log dir may not complete if future and current replicas segment files have different base offsets
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-8002
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8002
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.1.1
>            Reporter: Anna Povzner
>            Priority: Critical
>
> Once future replica fetches log end offset, the intended logic is to finish the move (and rename the future dir to current replica dir, etc). However, the check in Partition.maybeReplaceCurrentWithFutureReplica compares  the whole LogOffsetMetadata vs. log end offset. The resulting behavior is that the re-assignment will not finish for topic partitions that were cleaned/ compacted such that base offset of the last segment is different for the current and future replica. 
> The proposed fix is to compare only log end offsets of the current and future replica.



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