[
https://issues.apache.org/jira/browse/KAFKA-10143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17156937#comment-17156937
]
Randall Hauch commented on KAFKA-10143:
---------------------------------------
Temporarily removed `2.6.0` as the fix version so that we can cut 2.6.0 RC0.
This is an isolated regression, and we anticipate that we can have the
community begin testing RC0 and then we'll release RC1 with the limited
changes/fixes for this issue that should not invalidate any of the more general
testing we do with RC0.
As soon as RC0 is built, I'll add the fix version back.
> Can no longer change replication throttle with reassignment tool
> ----------------------------------------------------------------
>
> Key: KAFKA-10143
> URL: https://issues.apache.org/jira/browse/KAFKA-10143
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 2.6.0
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Priority: Blocker
>
> Previously we could use --execute with the --throttle option in order to
> change the quota of an active reassignment. We seem to have lost this with
> KIP-455. The code has the following comment:
> {code}
> val reassignPartitionsInProgress = zkClient.reassignPartitionsInProgress()
> if (reassignPartitionsInProgress) {
> // Note: older versions of this tool would modify the broker quotas
> here (but not
> // topic quotas, for some reason). This behavior wasn't documented in
> the --execute
> // command line help. Since it might interfere with other ongoing
> reassignments,
> // this behavior was dropped as part of the KIP-455 changes.
> throw new
> TerseReassignmentFailureException(cannotExecuteBecauseOfExistingMessage)
> }
> {code}
> Seems like it was a mistake to change this because it breaks compatibility.
> We probably have to revert. At the same time, we can make the intent clearer
> both in the code and in the command help output.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
