WIP: Add AutoScaling to K8s operator#6507
Open
ayushtkn wants to merge 2 commits into
Open
Conversation
|
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
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.



What changes were proposed in this pull request?
Add auto scaling to Hive Operator
Why are the changes needed?
Better usage & cloud saving.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Manually
Installed Dependencies
Started Hive Operator With AutoScaling Enabled
Launched Beeline
OUTPUTS:
Start -> Only 1 HMS, no services
Hits First Beeline Session -> HS2, Tez AM, LLAP Daemons starts
Quits the Beeline Session -> Wait for CoolDown Period -> The pods scales down to 0
Runs some load -> LLAP scales up from 1 -> 2 (max configured )
AutoScaling HS2 to 2 (Reduced max threshold)
And

AutoScaling HS2 2->1
AutoScaling HMS 1 -> 2
AutoScaling HMS 2 -> 1
AutoScaling to Idle Mode, HS2 & Gang -> 0