...
Three new configs will be added. All of these configs are cluster-wide which means they are global configs affecting the entire cluster.
| Config name | Type | Default | Valid values | Importance | Dynamic update mode | Description |
|---|---|---|---|---|---|---|
| reassignment.max.parallelconcurrent.leader.movements | int | Int.MAX | [1,...] | medium | cluster-wide | This new configuration would tell how many replicas of a single partition can be moved at once. |
| reassignment.max.parallelconcurrent.partition.count | int | Int.MAX | [1,...] | medium | cluster-wide | This configuration puts an upper limit on how many partition reassignments can be run concurrently. To calculate the sum of concurrent movements one can multiply this config by |
| reassignment.max.parallelconcurrent.replica.count | int | Int.MAX | [1,...] | medium | cluster-wide | This one puts an upper limit on concurrent leader movements. It is useful to reduce the controller burden on big reassignments. |
...
As an addition these values could be changed dynamically to somewhat "throttle" the reassignment. This kind of throttling would only affect the next reassignment step calculation and would leave the currently running one as it is. It might be better to throttle certain reassignment on a much more advanced way but it could also exceed the scope of this KIP.
...