-
Notifications
You must be signed in to change notification settings - Fork 354
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
fix: count determined-system pods as det pods [RM-148] #9148
Conversation
✅ Deploy Preview for determined-ui ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #9148 +/- ##
==========================================
+ Coverage 45.46% 45.48% +0.02%
==========================================
Files 1197 1197
Lines 147556 147558 +2
Branches 2438 2437 -1
==========================================
+ Hits 67092 67123 +31
+ Misses 80232 80203 -29
Partials 232 232
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
LGTM!
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.
minor feedback
can we add a test for this? |
aa77cbe
to
0b027c1
Compare
Ticket
RM-148
Description
If a pod has a "determined system", "determined preemption" OR "determined" label, don't count it as a "nonDet" pod. This fixes a bug where the db/master pods were counted twice as det pods & nonDet pods, and the master logs gave a
too many pods mapping to node
warning.Test Plan
Spin up your own small CPU cluster (or use mine -- slack me for the IP), and check that there are
# of slots - 2
slots left in the "default RM". This means that the db & master pod are being counted just once (correct). If there are fewer slots available than expected, or no slots free, this means the pods are being double counted.Additionally, try spinning up your own experiment and make sure you don't get the "too many pods" warning in your master logs.
Checklist
docs/release-notes/
.See Release Note for details.