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

[develop] Switch preliminary scale-all nodes attempt to be all-or-nothing #555

Merged
merged 2 commits into from
Aug 22, 2023

Conversation

lukeseawalker
Copy link
Contributor

Description of changes

Optimize job level scaling with preliminary scale-all nodes attempt. Switch this preliminary scaling from best-effort to all-or-nothing, so to remove unused instance launches

Tests

n/a

References

n/a

Checklist

  • Make sure you are pointing to the right branch.
  • If you're creating a patch for a branch other than develop add the branch name as prefix in the PR title (e.g. [release-3.6]).
  • Check all commits' messages are clear, describing what and why vs how.
  • Make sure to have added unit tests or integration tests to cover the new/modified code.
  • Check if documentation is impacted by this change.

Please review the guidelines for contributing and Pull Request Instructions.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Optimize job level scaling with preliminary scale-all nodes attempt.
Switch this preliminary scaling from best-effort to all-or-nothing, so to remove unused instance launches

Signed-off-by: Luca Carrogu <[email protected]>
@lukeseawalker lukeseawalker enabled auto-merge (rebase) August 22, 2023 06:54
@@ -776,7 +776,7 @@ def _scaling_for_jobs_multi_node(
self.unused_launched_instances |= self._launch_instances(
Copy link
Contributor

Choose a reason for hiding this comment

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

NIT: Let's fix the comment explaining this line of code (... preliminary scale-all nodes attempt ... -> ... preliminary all-or-nothing nodes attempt ...)

@lukeseawalker lukeseawalker merged commit e17bb8f into aws:develop Aug 22, 2023
10 checks passed
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.

2 participants