[ https://issues.apache.org/jira/browse/KAFKA-12681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jacky resolved KAFKA-12681. --------------------------- Resolution: Duplicate > Kraft MetadataPartitionsBuilder _localChanged and _localRemoved out of order > ----------------------------------------------------------------------------- > > Key: KAFKA-12681 > URL: https://issues.apache.org/jira/browse/KAFKA-12681 > Project: Kafka > Issue Type: Bug > Components: core > Affects Versions: 2.8.0 > Reporter: jacky > Priority: Minor > > In version 2.8, MetadataPartitionsBuilder has the field _localChanged and > _localRemoved which record the change and delete partition, but we always > process _localChanged partitions, and then _localRemoved in the > kafka.server.RaftReplicaManager#handleMetadataRecords, not respect the > original order, for example, > 1. migrate the partition p1 from b0 to b1; > 2. change the leader of p1 > 3.migrate p1 from b1 to b0 > and the _localRemoved will delete the p1 at last. -- This message was sent by Atlassian Jira (v8.3.4#803005)