You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: rebalance of topics with no config files (#245)
* feat(tube-3309): add initial groundwork for rebalancing of topics with no config files
* feat(tube-3309): use topic name instead of filename to keep track of existing generated files; wrap topic file and config traversal in reusable function
* feat(tube-3309): make use of wrapper processTopicFiles function for main process
* feat(tube-3309): update logic to skip existing config files
* Update cmd/topicctl/subcmd/rebalance.go
Co-authored-by: Peter Dannemann <28637185+petedannemann@users.noreply.github.com>
* update readme, name of flag, and logic to skip existing files
* Update README.md
Co-authored-by: Peter Dannemann <28637185+petedannemann@users.noreply.github.com>
---------
Co-authored-by: David Teutli <dapalacio@segment.com>
Co-authored-by: Peter Dannemann <28637185+petedannemann@users.noreply.github.com>
Copy file name to clipboardExpand all lines: README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -457,6 +457,8 @@ To rebalance **all** topics in a cluster, use the `rebalance` subcommand, which
457
457
function on all qualifying topics. It will inventory all topic configs found at `--path-prefix` for a cluster
458
458
specified by `--cluster-config`.
459
459
460
+
To rebalance topics in a cluster that exist without topic configuration files, use the `rebalance` subcommand with the `--bootstrap-missing-configs` flag. This will temporarily bootstrap any missing topic configs at `--path-prefix`. This can also be used to use topicctl as a topic rebalancing tool, without using its topic configuration management features
461
+
460
462
This subcommand will not rebalance a topic if:
461
463
462
464
1. the topic config is inconsistent with the cluster config (name, region, environment etc...)
0 commit comments