abhishekrb19 opened a new issue, #15951:
URL: https://github.com/apache/druid/issues/15951
### Affected Version
Versions 29.0.0 and below
### Description
Regardless of `druid.coordinator.kill.ignoreDurationToRetain` configuration,
the kill duty doesn't clean up segments that fall outside the "regular"
interval range. For example:
1. Any segment that ends at ends at `DateTimes.MAX`. This includes:
- `ALL` partitioned segments - `[DateTimes.MIN, DateTimes.MAX)`.
- Segments that starts at a finite time, but ends at `DateTimes.MAX`, for
example: `[2020, DateTimes.MAX)`.
3. Segments outside the regular string comparison range, such as
`0001-01-01T00Z/19940-01-01T00Z`.
This is because the kill duty `KillUnusedSegments` uses
`DateTimes.COMPARE_DATE_AS_STRING_MAX` in the
Datetime string comparison for the end endpoint when retrieving unused
segment intervals.
For example, if the segment on disk has an interval outside this range,
`[0001-01-01T00Z/19940-01-01T00Z]`,
while the interval queried is `[2020/2021]`, string comparison would return
the result that '19940' < '2020', which
excludes the segment, even though it does overlap.
The eternity use case (1) is a more common scenario that it can use some
special handling.
--
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]
