This message was deleted.

I think Request Logging and metrics should be able to track each query in the broker and historical by their query ID.

Thanks @Sergio Ferragut. While the document suggests broker tiering have a dependency on historical tiering, I don’t see there is a linkage between broker tiers and historical tiers. Is the tierToBrokerMap used to link between broker tiers and historical tiers?

I think that there are two levels of setup for this (three if you include the query context). The router and how it decides to select a broker (

druid.router.strategies

) for a given request and the broker/historical config which decides which set of historicals to use to resolve a query. The query context also plays a role if you want specific queries to default to running on a particular tier (by specifying the

brokerService

) or by giving the query a

priority

when using priority based routing strategy where the brokers have a priority designation. Broker priority is based on

druid.router.tierToBrokerMap

where highest priority is broker tier that is listed first. I haven't tried this myself, but that is how I understand this. Let us know how it goes.

Thanks Sergio. Appreciate your response.