capistrant opened a new issue, #13497: URL: https://github.com/apache/druid/issues/13497
### Description Currently the coordinator provides the facility to provide a list of datasources that are permissible to kill. You can also leave that list blank and allow all datasources to be killed. This is great when the number of datasources is small, but eventually the inverse of the current config becomes more convenient for an operator. For instance, if my cluster has 100 datasources and I want to kill 90 of them + any newly created datasources, I'd rather put the 10 protected datasources on a skipList and let everything else be killed as needed. The open question is how to reconcile the existence of these two competing configs. I think the easiest way would be to ban the ability to have both lists populated, an operator would have to choose one or the other. ### Motivation Please provide the following for the desired feature or change: * if my cluster has 100 datasources and I want to kill 90 of them + any newly created datasources, I'd rather put the 10 protected datasources on a skipList and let everything else be killed as needed. * makes operating a cluster with many datasources more efficient -- 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]
