From 8c12c59bf974b0c561006f18e2049d05fc793d35 Mon Sep 17 00:00:00 2001 From: Manan Gupta Date: Fri, 24 Jan 2025 15:49:26 +0530 Subject: [PATCH] feat: add summary changes Signed-off-by: Manan Gupta --- changelog/22.0/22.0.0/summary.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/changelog/22.0/22.0.0/summary.md b/changelog/22.0/22.0.0/summary.md index c6c1eb0148e..b3916b8f0e8 100644 --- a/changelog/22.0/22.0.0/summary.md +++ b/changelog/22.0/22.0.0/summary.md @@ -136,7 +136,7 @@ The base system now uses Debian Bookworm instead of Debian Bullseye for the `vit ### KeyRanges in `--clusters_to_watch` in VTOrc VTOrc now supports specifying KeyRanges in the `--clusters_to_watch` flag. This is useful in scenarios where you don't need to restart a VTOrc instance if you run a reshard. -For example, if a VTOrc is configured to watch `ks/-80`, then it would watch all the shards that fall under the KeyRange `-80`. If a reshard is run and, `-80` is split into new shards `-40`, and `40-80`, the VTOrc instance will automatically start watching the new shard without needing a restart. +For example, if a VTOrc is configured to watch `ks/-80`, then it would watch all the shards that fall under the KeyRange `-80`. If a reshard is run and, `-80` is split into new shards `-40`, and `40-80`, the VTOrc instance will automatically start watching the new shard without needing a restart. In the previous logic, watching a shard -80 would watch 1 (or 0) shard only. In the new system, since we interpret -80 as a key range, it can lead to a watch on multiple shards as described in the example. The users can still continue to specify exact key ranges too, and the new feature is backward compatible. ### Support for Filtering Query logs on Error