-
Notifications
You must be signed in to change notification settings - Fork 7k
Open
Labels
P2Important issue, but not time-criticalImportant issue, but not time-criticalcoreIssues that should be addressed in Ray CoreIssues that should be addressed in Ray Corecore-clustersFor launching and managing Ray clusters/jobs/kubernetesFor launching and managing Ray clusters/jobs/kubernetesenhancementRequest for new feature and/or capabilityRequest for new feature and/or capability
Description
Description
A best practice with spot instances is to specify many different instance types so that the user is more likely to have their request satisfied by some combination of instance types.
Currently we can specify multiple instance types, but it's not clear what happens when we do (#39788)
One option to handle this is to create an EC2 Fleet instead of requesting individual node types
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-fleet.html
This feature offloads all the logic about which instances to start to AWS. The autoscaler then only needs to change the target capacity of the fleet to match the number of CPUs requested.
Use case
No response
zakajd and SlowShip
Metadata
Metadata
Assignees
Labels
P2Important issue, but not time-criticalImportant issue, but not time-criticalcoreIssues that should be addressed in Ray CoreIssues that should be addressed in Ray Corecore-clustersFor launching and managing Ray clusters/jobs/kubernetesFor launching and managing Ray clusters/jobs/kubernetesenhancementRequest for new feature and/or capabilityRequest for new feature and/or capability