Warn user when overriding requests but not limits#2151
Merged
Conversation
Signed-off-by: Fabio Grätz <fabiogratz@googlemail.com>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2151 +/- ##
===========================================
+ Coverage 50.76% 85.80% +35.03%
===========================================
Files 176 313 +137
Lines 17116 23581 +6465
Branches 3530 3531 +1
===========================================
+ Hits 8689 20233 +11544
+ Misses 8000 2738 -5262
- Partials 427 610 +183 ☔ View full report in Codecov by Sentry. |
Future-Outlier
approved these changes
Jan 31, 2024
2 tasks
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why are the changes needed?
As a user, I would expect that the resulting task pod has 5 vCPUs and 5Gi or RAM. Turns out, the task pod has 3 each!
This behaviour is very unintuitive, the reason being as follows:
What changes were proposed in this pull request?
In this PR I add a warning so that at least users are warned to set limit as well.
How was this patch tested?
Running the above workflow with
pyflyte -v run --remote ...results in the following new log line:Requests overridden on node n0 (<FlyteLiteral name: "foo" retries { }>) without specifying limits. Requests are clamped to original limits.The fact that
-vis required to see this warning unfortunately limits its usefulness. Maybe this warrants a discussion whether this behaviour should be changed.