-
Notifications
You must be signed in to change notification settings - Fork 135
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
RDoc-3011 & RDoc-3012 Add autoscaling feature description #1918
Merged
Conversation
This file contains 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
hiddenshadow21
changed the title
RDoc-3012 Add autoscaling feature description
RDoc-3011 & RDoc-3012 Add autoscaling feature description
Oct 3, 2024
PFYasu
reviewed
Oct 11, 2024
|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| | ||
| Highest Type | The maximum virtual machine size (inclusive) available for upscaling | | ||
| Upscaling Grace Period | The time delay before upscaling begins after a high resource threshold is exceeded, allowing the system to avoid immediate scaling. | | ||
| High Cpu Threshold | The average CPU usage percentage from last *High CPU Threshold Duration* that triggers the upscaling process. | |
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.
Suggested change
| High Cpu Threshold | The average CPU usage percentage from last *High CPU Threshold Duration* that triggers the upscaling process. | | |
| High Cpu Threshold | The average CPU usage percentage from last *High CPU Threshold Duration* that triggers the upscaling process. | |
PFYasu
reviewed
Oct 11, 2024
|
||
| Parameter | Description | | ||
|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| | ||
| Highest Type | The maximum virtual machine size (inclusive) available for upscaling | |
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.
Suggested change
| Highest Type | The maximum virtual machine size (inclusive) available for upscaling | | |
| Highest Type | The maximum virtual machine size (inclusive) available for upscaling. | |
PFYasu
reviewed
Oct 11, 2024
| Upscaling Grace Period | The time delay before upscaling begins after a high resource threshold is exceeded, allowing the system to avoid immediate scaling. | | ||
| High Cpu Threshold | The average CPU usage percentage from last *High CPU Threshold Duration* that triggers the upscaling process. | | ||
| High Cpu Threshold Duration | The duration for which the average CPU usage must exceed the threshold before triggering upscaling. | | ||
| Upscaling Step | Determines by how many instances upscaling should take place in one go. For example with step set to 2 it will scale up from *Dev10* to *Dev30* | |
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.
Suggested change
| Upscaling Step | Determines by how many instances upscaling should take place in one go. For example with step set to 2 it will scale up from *Dev10* to *Dev30* | | |
| Upscaling Step | Determines by how many instances upscaling should take place in one go. For example with step set to 2 it will scale up from *Dev10* to *Dev30*. | |
PFYasu
approved these changes
Oct 11, 2024
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.
https://issues.hibernatingrhinos.com/issue/RDoc-3012