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

Posted to dev@kafka.apache.org by "Igor Soarez (Jira)" <ji...@apache.org> on 2024/05/04 20:26:00 UTC

[jira] [Resolved] (KAFKA-16624) Don't generate useless PartitionChangeRecord on older MV

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

Igor Soarez resolved KAFKA-16624.
---------------------------------
    Resolution: Fixed

> Don't generate useless PartitionChangeRecord on older MV
> --------------------------------------------------------
>
>                 Key: KAFKA-16624
>                 URL: https://issues.apache.org/jira/browse/KAFKA-16624
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Colin McCabe
>            Assignee: Colin McCabe
>            Priority: Minor
>
> Fix a case where we could generate useless PartitionChangeRecords on metadata versions older than 3.6-IV0. This could happen in the case where we had an ISR with only one broker in it, and we were trying to go down to a fully empty ISR. In this case, PartitionChangeBuilder would block the record to going down to a fully empty ISR (since that is not valid in these pre-KIP-966 metadata versions), but it would still emit the record, even though it had no effect.



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