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

Resource view - reconcile inconsistencies between metrics of different topologies #2389

Open
fbarl opened this issue Mar 24, 2017 · 1 comment
Labels
accuracy Incorrect information is being shown to the user; usually a bug bug Broken end user or developer functionality; not working as the developers intended it

Comments

@fbarl
Copy link
Contributor

fbarl commented Mar 24, 2017

As @2opremio has predicted, having multiple sources of truths for the nodes' metrics between hosts, containers and processes topologies is making some processes in the resource view seem as if they were consuming more resources than their parent containers.

resources

To prevent resource boxes rendering overflows (and overlaps) in such cases, a temporary hack is used that renormalizes the total length of the overflown children to perfectly fit on top of their parent. This is just a visual fix though and it doesn't affect the displayed metric info in any way.

A proper solution would probably require backend to draw all the metrics info from a single source so that:

  • the total resource utilization of children could never exceed the parent's
  • resource capacities info was (more) consistent between different topologies
@fbarl fbarl added accuracy Incorrect information is being shown to the user; usually a bug bug/P1 labels Mar 24, 2017
@rade rade added bug Broken end user or developer functionality; not working as the developers intended it and removed bug/P1 labels Mar 25, 2017
@rade
Copy link
Member

rade commented May 18, 2017

The underlying problem is #1133.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accuracy Incorrect information is being shown to the user; usually a bug bug Broken end user or developer functionality; not working as the developers intended it
Projects
None yet
Development

No branches or pull requests

2 participants