This message was deleted.
# troubleshooting
s
This message was deleted.
i
If the data is in deep storage, it should load as per the rules. Do you see the load queues taking on the segments or do you see in the logging if the older segments are being loaded?
r
@Ian Roberts I am not sure how to check, i am running query to validate this where i am still not able to older date data after extending retention.
i
Check your coordinator log to see if it is assigning segments to historicals. Depending on when you changed the retention settings, it can take time to load the older segments. You can also check the segments tab to find the earliest timestamp of the loaded segments
g
Once it's marked unused (by drop rules) it will not automatically be marked used even if you change the rules
i
interesting, so the metadata still will have it marked as unused?
g
yeah, automated marking only goes one way
once it's been marked unused automatically, you can mark it used manually, as long as you haven't done a permanent deletion yet through kill task (https://druid.apache.org/docs/latest/data-management/delete.html#permanently-kill-task) or autokill
IIRC there's an action in the web console to re-mark a certain time interval as used
there is also an API for it of course; you can do it by interval or for an entire datasource
i
Thank you!
r
Thanks, these are very helpful inputs. i couldn't find any option in UI where i could mark it as used manually, segments are still available in s3 location. also, to confirm i don't see segments in the date range which i extended, so i believe it has to be marked manually which i am trying to figure out an option in UI or how to submit through an Api. Any suggestions please. cc @Gian Merlino @Ian Roberts
v
In the datasources view you can mark segments as used
Also be aware that you are on a fairly old Druid version (notice how my screenshot is blueish and yours is greenish), the UI evolved a ton so it is possible some options that people suggest via screenshots (like I did) might not be in the same place for you (or might not exist)
r
great, thanks for recommending, i will propose to move to latest internally. i was able to set interval as 2022-08-25T000000.00/2022-09-13T000000.00. However, i see only 1 day data got loaded which was of 12th since more than 30 mins. in coordinator node, i see an error, not sure if that has caused it not to reload-
Copy code
2022-09-27T15:27:54,368 WARN [ServerInventoryView-0] org.apache.druid.curator.inventory.CuratorInventoryManager - Exception while getting data for node /test-druid-base/druid/segments/stats-druid-historical-1.test-druid-historical.test-uat.svc.cluster.local:8083/test-druid-historical-1.test-druid-historical.test-uat.svc.cluster.local:8083_historical_tier1_2022-09-27T15:24:57.586Z_142b7f8576e44979a4c787f0f6472dbe230
org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = NoNode for /test-druid-base/druid/segments/test-druid-historical-1.test-druid-historical.test-uat.svc.cluster.local:8083/test-druid-historical-1.test-druid-historical.test-uat.svc.cluster.local:8083_historical_tier