[ https://issues.apache.org/jira/browse/KAFKA-16218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Drawxy updated KAFKA-16218: --------------------------- Affects Version/s: 3.1.2 > Partition reassignment can't complete if any target replica is out-of-sync > -------------------------------------------------------------------------- > > Key: KAFKA-16218 > URL: https://issues.apache.org/jira/browse/KAFKA-16218 > Project: Kafka > Issue Type: Bug > Affects Versions: 3.1.2 > Reporter: Drawxy > Priority: Major > > Assumed that there were 4 brokers (1001,2001,3001,4001) and a topic partition > _foo-0_ (replicas[1001,2001,3001], isr[1001,3001]). The replica 2001 can't > catch up and become out-of-sync due to some issue. > If we launch a partition reassinment for this _foo-0_ (the target replica > list is [1001,2001,4001]), the partition reassignment can't complete even if > the adding replica 4001 already catches up. At that time, the partition state > would be replicas[1001,2001,4001,3001] isr[1001,3001,4001]. > > The out-of-sync replica 2001 shouldn't make the partition reassignment stuck. -- This message was sent by Atlassian Jira (v8.20.10#820010)