-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Fix host metrics on overprovisioning change #12403
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
Open
vishesh92
wants to merge
1
commit into
apache:4.20
Choose a base branch
from
shapeblue:fix-capacity-overcommit
base: 4.20
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+10
−22
Open
Changes from all commits
Commits
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 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
Oops, something went wrong.
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.
There seems to be some intentional logic behind the old code:
ramOvercommitRatiois saved in VM settings (which is set equal to the clusterOvercommitRatio whenever the VM is started)clusterRamOvercommitRatiois the current ratio set on the cluster.The idea behind the old code seems to be that for running VMs the used stats are kept at the same ratio to the total capacity.
For example, let's say total capacity is 64G and a VM is using 32G (Half of the total capacity)
Now, the
clusterOvercommitRatiois changed from 1 to 2.The VM's used will change to 64G (32/1 * 2). This means the running VM is still using half of the total capacity of the host.
The logic seems to be a safeguard against a running VM not getting affected by sudden capacity jumps using the overCommit ratio of the cluster.
Think of a little extreme case when clusterOvercommitRatio is changed from 1 to 5. Without this change, it is bound to affect the running VM which might not be intended.
When the VM restarts, its
ramOvercommitRatiowill change to 2. The VM used will then become 32G (32/2 * 2).Basically the logic seems to be that running VMs should not be affected by sudden jumps in the clusterOvercommitRatio.
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.
cc @vishesh92 @DaanHoogland @NuxRo
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.
you are asking if this change is functionaly sane @abh1sar?
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 @DaanHoogland , I think the behaviour is by design and this change will affect functionality