Skip to content
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

[YUNIKORN-2150] Node resource utilization chart does not render properly #147

Closed
wants to merge 1 commit into from

Conversation

chenyulin0719
Copy link
Contributor

What is this PR for?

Fix the node resource utilization chart so it can correctly render with dominant resource.

What type of PR is it?

  • - Bug Fix
  • - Improvement
  • - Feature
  • - Documentation
  • - Hot Fix
  • - Refactoring

Todos

NA

What is the Jira issue?

https://issues.apache.org/jira/browse/YUNIKORN-2150

How should this be tested?

make test should pass. )
Run kubectl port-forward svc/yunikorn-service 9889 9080 -n yunikorn to forward yunikron rest endpoint.
(Do remember to update the core version.)
Open another teminal and runyarn start and check the result of http://localhost:4200/#/dashboard

Screenshots (if appropriate)

After YUNIORN-2150

Questions:

NA

@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (271bb72) 66.66% compared to head (7887dbb) 66.66%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #147   +/-   ##
=======================================
  Coverage   66.66%   66.66%           
=======================================
  Files           1        1           
  Lines          30       30           
=======================================
  Hits           20       20           
  Misses          7        7           
  Partials        3        3           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@wilfred-s wilfred-s left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
Tested in a local setup with a 3 node kind cluster and see the usage change.

@wilfred-s wilfred-s closed this in d1a26e7 Nov 15, 2023
wilfred-s pushed a commit that referenced this pull request Nov 15, 2023
Node resource utilization chart does not render properly as it expects
multiple resources types. Node utilisation REST was changed to dominant
resource only.i
Multiple resource types in the REST response  could lead to showing the
incorrect usage (non dominant one) or for different types after a
reload. The REST content shows types in a random way.

Closes: #147

Signed-off-by: Wilfred Spiegelenburg <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants