mshahid6 opened a new issue, #18964: URL: https://github.com/apache/druid/issues/18964
### Motivation Currently, Druid has a coordinator config but no broker-level dynamic config which can be appropriate for features like query blacklist enforcement, data aliases, routing rules, feature flags etc. The primary motivation for having a broker config is for blacklisting queries dynamically in the situation there is a rogue app/user spamming the cluster without relying on static configs/restarts. ### Proposed changes #### Broker config Similar to CoordinatorDynamicConfig, introduce a broker-level dynamic config persisted in metadata store, polled periodically by brokers. Admin APIs to GET and POST configs (UI can be added later). #### Query Blacklist Enforce at broker query lifecycle, blacklist based on datasource in query or additionally, query context matches, querytype, remote address etc. ### Rationale Alternatively, we could reuse coordinator dynamic config for query blacklisting but it is not the appropriate enforcement point and would require broker to pull coordinator config. Moreover, broker config can be used for other future features such as datasource aliasing, routing rules or feature flags. -- 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]
