-
Notifications
You must be signed in to change notification settings - Fork 4k
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
(stepfunctions-tasks): EMR createCluster command, add Instances > InstanceFleets > LaunchSpecifications > OnDemandSpecification #12501
Comments
…trategy for emrcreatecluster step The current InstanceFleetProvisioningSpecificationsProperty (https://docs.aws.amazon.com/cdk/api/latest/docs/@aws-cdk_aws-stepfunctions-tasks.EmrCreateCluster.InstanceFleetProvisioningSpecificationsProperty.html) only supports spot specification whereas the EMR InstanceFleetProvisioningSpecifications supports OnDemandSpecification (https://docs.aws.amazon.com/emr/latest/APIReference/API_InstanceFleetProvisioningSpecifications.html#EMR-Type-InstanceFleetProvisioningSpecifications-OnDemandSpecification). This commit adds the missing options. fixes aws#12501
…trategy for emrcreatecluster step The current InstanceFleetProvisioningSpecificationsProperty (https://docs.aws.amazon.com/cdk/api/latest/docs/@aws-cdk_aws-stepfunctions-tasks.EmrCreateCluster.InstanceFleetProvisioningSpecificationsProperty.html) only supports spot specification whereas the EMR InstanceFleetProvisioningSpecifications supports OnDemandSpecification (https://docs.aws.amazon.com/emr/latest/APIReference/API_InstanceFleetProvisioningSpecifications.html#EMR-Type-InstanceFleetProvisioningSpecifications-OnDemandSpecification). This commit adds the missing options. fixes aws#12501
Is this being actively developed? This a feature that would be a big win for our current Step Function and make migrating to flexible fleets incredibly easy for our team. Otherwise, we will need to re-haul our step function. |
This issue has not received any attention in 1 year. If you want to keep this issue open, please leave a comment below and auto-close will be canceled. |
This feature will benefit our team a lot. We have many StepFunctions state machines with most steps running on EMR. Creating an EMR cluster with OnDemandSpecification in Sfn with CDK will make our job a lot more efficient. |
This becomes really crucial where required. It would be really helpful if this can be picked up. |
FYI this cannot be used with |
Created duplicate here #27761 -- feel free to follow progress. |
The current InstanceFleetProvisioningSpecificationsProperty (https://docs.aws.amazon.com/cdk/api/latest/docs/@aws-cdk_aws-stepfunctions-tasks.EmrCreateCluster.InstanceFleetProvisioningSpecificationsProperty.html) only supports spot specification whereas the EMR InstanceFleetProvisioningSpecifications supports OnDemandSpecification (https://docs.aws.amazon.com/emr/latest/APIReference/API_InstanceFleetProvisioningSpecifications.html#EMR-Type-InstanceFleetProvisioningSpecifications-OnDemandSpecification). I would like the functionality to add OnDemandSpecifications for our usecase.
Use Case
Functional parity with options available in EMR and for our internal use where we need to specify AllocationStrategy under OnDemandSpecifications.
Proposed Solution
Add OnDemandProvisioningSpecificationProperty type with allocationStrategyProperty. Add a field called onDemandSpecification to InstanceFleetProvisioningSpecificationsProperty here. https://github.com/aws/aws-cdk/blob/master/packages/%40aws-cdk/aws-stepfunctions-tasks/lib/emr/emr-create-cluster.ts#L598
Finally modify this function (https://github.com/aws/aws-cdk/blob/master/packages/%40aws-cdk/aws-stepfunctions-tasks/lib/emr/private/cluster-utils.ts#L123) to emit the relevant parameters for ondemand specification.
Other
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: