Support placement groups for elastic fleets#3282
Merged
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
1 participant
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.
Closes #3256
Previously, placement groups were created and used for instances provisioned for static cloud fleets (with
nodes: n). This PR adds placement group support for any instances provisioned in cluster fleets. It repeats placement group logic from create_instance in process_submitted_jobs. Also fixes several fleet-related bugs introduced in previous PRs.Important: Provisioning even one instance in a cluster fleet (e.g. for a dev env) now creates a placement group for that instance since more instances can be provisioned later due to fleet elasticity and all the instances should be in the placement group.