-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Backend] Cache - Add cache_enabled label for cache filtering #3352
Merged
Merged
Changes from 14 commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
6994984
Initial execution cache
rui5i 1534782
Merge branch 'master' of https://github.com/kubeflow/pipelines
rui5i d5ce005
Merge branch 'master' of https://github.com/kubeflow/pipelines
rui5i fdb3ba4
fix master
rui5i 2b69c1e
Merge branch 'master' of https://github.com/kubeflow/pipelines
rui5i 6a4dca2
Merge branch 'master' of https://github.com/kubeflow/pipelines
rui5i deb279d
Merge branch 'master' of https://github.com/kubeflow/pipelines into k…
rui5i 96a8ef7
Add cache enabled annotation to pod annotaion for cache filtering
rui5i 6087d7e
fix go.sum
rui5i 3de2556
Add cache disable annotation value for future use
rui5i 68f1467
Rename annotation key to cache qualified
rui5i d2d94b6
revert cache_qualified to cache_enabled
rui5i 58d924d
Fix code comment
rui5i 3d4c34e
Change cache_enabled annotation to label
rui5i 366a907
Add value check
rui5i d64cefb
Merge branch 'master' of https://github.com/kubeflow/pipelines into k…
rui5i 98c77fb
Read cache_enabled flag from config
rui5i c508668
Add comments on set template labels
rui5i File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this code skip setting the cache value if it exists? This way it will respect user's input if user disable the cache for a given step.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. The cache server will only receive the pod with labels: cache_enabled = true. In the future we can have UI support with toggling cache behavior for a run with this label. Per step cache behavior control will be base on MaxCacheStaleness.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Per-step cache disabling is performed using a different mechanism (setting task.max_cache_staleness = "0").
I'm OK with not changing the value if it already exists. But it should not exist since it's a vendored label and SDK does not set it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit confused. Do we have two flags to control the cache for a given step, cache_enabled and max_cache_staleness? if one supersets the other, we should consider dedup them.
If cache_enabled is not exposed to end user, what's the purpose of having it? Should it be a feature flag at the caching server side, instead of at the workflow side?