[jira] [Updated] (KAFKA-19736) KAFKA-15665 prevents safe reassignments from completing

["Alyssa Huang (Jira)" <ji...@apache.org>]

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

Alyssa Huang updated KAFKA-19736:
---------------------------------
    Description: 
The implementation for KAFKA-15665 is a little too strict - it requires that all replicas in the target replica set be in ISR.

This means if we have a reassignment like [1, 2, 3] -> [2, 3, 4] where broker 2 was unhealthy and lagging in replication, reassignment would not complete. 

 

I believe it should work to instead just check the following:

- Added replicas are in ISR (newTargetISR)
- Resulting ISR (newTargetISR) is not under-min-isr

  was:
The implementation for KAFKA-15665 is a little too strict - it requires that all replicas in the target replica set be in ISR.

This means if we have a reassignment like [1, 2, 3] -> [2, 3, 4] where broker 2 was unhealthy and lagging in replication, reassignment would not complete. 


> KAFKA-15665 prevents safe reassignments from completing
> -------------------------------------------------------
>
>                 Key: KAFKA-19736
>                 URL: https://issues.apache.org/jira/browse/KAFKA-19736
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Alyssa Huang
>            Priority: Major
>
> The implementation for KAFKA-15665 is a little too strict - it requires that all replicas in the target replica set be in ISR.
> This means if we have a reassignment like [1, 2, 3] -> [2, 3, 4] where broker 2 was unhealthy and lagging in replication, reassignment would not complete. 
>  
> I believe it should work to instead just check the following:
> - Added replicas are in ISR (newTargetISR)
> - Resulting ISR (newTargetISR) is not under-min-isr



--
This message was sent by Atlassian Jira
(v8.20.10#820010)