This is an automated email from the ASF dual-hosted git repository.
kfaraz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/druid.git
The following commit(s) were added to refs/heads/master by this push:
new ffaaf1d788f Add documentation for druid.broker.segment.watchedTiers
(#19027)
ffaaf1d788f is described below
commit ffaaf1d788fd93a5a0ad54c75bc40f422d628f3f
Author: aho135 <[email protected]>
AuthorDate: Wed Feb 18 20:07:20 2026 -0800
Add documentation for druid.broker.segment.watchedTiers (#19027)
---
docs/operations/mixed-workloads.md | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/docs/operations/mixed-workloads.md
b/docs/operations/mixed-workloads.md
index 032f25b5e21..d99fb898772 100644
--- a/docs/operations/mixed-workloads.md
+++ b/docs/operations/mixed-workloads.md
@@ -191,6 +191,26 @@ druid.broker.select.tier=highestPriority
See [Broker configuration](../configuration/index.md#broker-process-configs)
for more details on these properties.
+#### Restrict Broker visibility to specific tiers
+
+By default, a Broker watches all Historical tiers for segment availability.
Use `druid.broker.segment.watchedTiers` to restrict a Broker to only see
segments on specific tiers. This provides strict query isolation - segments on
unwatched tiers are invisible to the Broker and cannot be queried by it.
+
+Example config for a Broker that only queries Historicals in a tier named
"hot":
+```
+druid.broker.segment.watchedTiers=["hot"]
+```
+
+Example config for a Broker that queries multiple tiers:
+```
+druid.broker.segment.watchedTiers=["hot","_default_tier"]
+```
+
+Note the difference between `druid.broker.select.tier` and
`druid.broker.segment.watchedTiers`:
+- `druid.broker.select.tier` controls **preference** among visible tiers
(which tier to query first)
+- `druid.broker.segment.watchedTiers` controls **visibility** (which tiers the
Broker can see at all)
+
+If a segment does not exist on the tiers watched by a Broker, it will not be
aware of that segment and queries for that data will return partial or no
results.
+
#### Configure query routing
Direct the Router to route queries appropriately by setting the default Broker
tier and the map of Historical tier to Broker tier in the
`router/runtime.properties` file.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
