capistrant opened a new issue #10876: URL: https://github.com/apache/druid/issues/10876
### Description Right now, `druid.coordinator.kill.durationToRetain` must be a positive duration. The `KillUnusedSegments` class subtracts the milliseconds value of this Duration from "now" when it is creating the upper bound on the interval "end" date that it uses when looking for segments eligible to kill. This change would remove that requirement of a positive duration for the configuration. A negative duration would translate into allowing kill tasks to be submitted against unused segments whose intervals end in the future. ### Motivation Please provide the following for the desired feature or change: - A detailed description of the intended use case, if applicable > There is nothing that prevents clusters from having segments that have intervals in the future as compared to "now". Things such as data forecasts could be an example. If these exist and become unused, there should be a way to have them cleaned up automatically just like segments whose interval end comes before "now". - Rationale for why the desired feature/change would be beneficial > Helps operators keep deep storage and metadata storage clean. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
