THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Table of Contents |
|---|
Status
Current state: Under Discussion Draft
Discussion thread:
JIRA:
| Jira | ||||||
|---|---|---|---|---|---|---|
|
...
| Config name | Type | Default | Valid values | Importance | Dynamic update mode |
|---|---|---|---|---|---|
| leader.reassignment.throttled.rate | Long | Long.MAX_VALUE | [1,...] | medium | per-broker |
| follower.reassignment.throttled.rate | Long | Long.MAX_VALUE | [1,...] | medium | per-broker |
Behavior-wise they'd throttle the addingReplicas of the LeaderAndIsrRequest during reassignment. Also leader.replication.throttled.replicas and follower.replication.throttled.replicas wouldn't be applied to these replicas as long as they're not in ISR. Once they enter it, they'd be allowed to have the replication bandwidth.
To change these configs, the user must have ALTER_CONFIG privilege on the given cluster config (as imposed by the incrementalAlterConfigs API which will be the medium for applying the configuration).
Reassignment Tool
The --throttle option's behavior in kafka-reassign-partitions.sh would change as it would use the new configs going forward. If there is need for reproducing the old behavior then it would still be possible by calling kafka-configs.sh manually before and after the reassignment to set the correct replication throttling.
...