kfaraz commented on code in PR #19027: URL: https://github.com/apache/druid/pull/19027#discussion_r2820346236
########## 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 through it. + +Example config for a Broker that only queries hot tier Historicals: Review Comment: ```suggestion Example config for a Broker that only queries Historicals in a tier named "hot": ``` ########## 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 through it. + +Example config for a Broker that only queries hot tier Historicals: +``` +druid.broker.segment.watchedTiers=["hot"] +``` + +Example config for a Broker that queries both hot and cold 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 only exists on a tier not in `watchedTiers`, the Broker will not be aware of that segment and queries for that data will return partial or no results. Review Comment: ```suggestion 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. ``` ########## 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 through it. Review Comment: ```suggestion 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. ``` ########## 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 through it. + +Example config for a Broker that only queries hot tier Historicals: +``` +druid.broker.segment.watchedTiers=["hot"] +``` + +Example config for a Broker that queries both hot and cold tiers: Review Comment: ```suggestion Example config for a Broker that queries multiple tiers: ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
