coordinator not loading historical data
- Dominant language
- Java
- Stars
- 14.1k
- Forks
- 3.8k
- Avg merge
- 2d 58m
- Merged PRs (30d)
- 233
Description
### Affected Version
0.16.0
### Description
I changed my datasource retention from `P1D` to `P4D`, yet only 1 day of data is loaded and console still says datasource is fully available.
This datasource is over 6 months old so i know older data exists in s3.


i wonder if this is related to #9040 (note that i dont see the datasource `kube-metrics-30m` in the error logs)
Contributor guide
Research direction
The report names no source files, tests, or entry points. Start by reproducing the retention change on the affected Druid datasource and inspect coordinator logs and historical-data loading behavior; the issue does not define a code-level completion condition beyond loading the expected historical data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100