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

Introduce autoscaling decisions #53934

Merged
merged 6 commits into from
Mar 24, 2020

Conversation

jasontedor
Copy link
Member

This is the first in a series of commits that will introduce the autoscaling deciders framework. This commit introduces the basic framework for representing autoscaling decisions.

This is the first in a series of commits that will introduce the
autoscaling deciders framework. This commit introduces the basic
framework for representing autoscaling decisions.
Copy link
Contributor

@henningandersen henningandersen left a comment

Choose a reason for hiding this comment

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

LGTM.


}

public static class MultipleAutoscalingDecision extends AutoscalingDecision {
Copy link
Contributor

Choose a reason for hiding this comment

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

I would prefer to not extend AutoscalingDecision. This could let AutoscalingDecision be a final class and we avoid throwing UnsupportedOperationException below (and remove decisions() from single decision).

Autoscaling deciders should not really have to choose between using a single or multi decision. The multi-decision is only for the "framework". MultipleAutoscalingDecision could be an inner class to AutoscalingService or co-located with the service.

I know this is contrary to lots of other code, so please consider this optional.

Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks for the input. I have made a refactoring here. Would you let me know your thoughts?

Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks for doing the refactor, this looks great.

jasontedor and others added 4 commits March 23, 2020 17:13
…k/autoscaling/AutoscalingDecisionTests.java

Co-Authored-By: Henning Andersen <33268011+henningandersen@users.noreply.github.com>
…k/autoscaling/AutoscalingDecisionTests.java

Co-Authored-By: Henning Andersen <33268011+henningandersen@users.noreply.github.com>
@jasontedor
Copy link
Member Author

@elasticmachine update branch

@jasontedor jasontedor merged commit 94e81b0 into elastic:master Mar 24, 2020
@jasontedor jasontedor deleted the autoscaling-decisions branch March 24, 2020 03:01
jasontedor added a commit that referenced this pull request Mar 24, 2020
This is the first in a series of commits that will introduce the
autoscaling deciders framework. This commit introduces the basic
framework for representing autoscaling decisions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants