https://flyte.org logo
Join Slack
Powered by
I did a search among some GitHub issues but didn't...
# flyte-support
c
I did a search among some GitHub issues but didn't see something with regards to supporting TTLs for cached tasks. We have some cached tasks that started to fail after some blob store retention policies deleted the underlying 
FlyteFile
contents. We've evaluated ways to work around this and one of the things we considered was allowing TTLs to be added to the task caching metadata.
h
There is a config on propeller (maxCache something) that controls the global TTL for reading cached outputs
I would set that to 1/2 the s3 retention period
It doesn't give you the granularity you're looking for maybe?
c
I think that would work. We may have mis-interpreted what that config setting would do. Thank you!
Just checked with the team and it looks like our TTLS are quite dynamic (blob stores configured on a per-project basis) so having something global would be not ideal. We'll probably implement something on our end
h
Cool.. if you can actually upstream that, I think it can be quite useful for others as well
Are you thinking of attaching TTL and passing that down to the catalog service? Or just using it on cache read in propeller (similar to the global config but per task)?
c
I'm not sure yet, haven't dug into the code yet. But I'll keep any pointers you have in mind
f
@clean-glass-36808 i think passing the TTL and just checking it in propeller would be great. Ideally we should pass the TTL to cache service, so that it can return immediately without the penalty of loading data
Open in Slack
PreviousNext
Powered by