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

Trying the Spot + Ondemand in Managed Autoscaling configuration, but there is ParamValidation Exception #3963

Closed
Pram098 opened this issue Dec 1, 2023 · 3 comments
Assignees
Labels
emr response-requested Waiting on additional information or feedback. service-api This issue is caused by the service API, not the SDK implementation.

Comments

@Pram098
Copy link

Pram098 commented Dec 1, 2023

Describe the bug

Hi, recently i am testing the functionality where i was thinking of using few cores as on-demand and few core nodes as spot, but there seems to be validation exception, when i manually tried the same config in EMR, it is allowing those values.

{
"ComputeLimits": {
"UnitType": "Instances",
"MinimumCapacityUnits": 2,
"MaximumCapacityUnits": 26,
"MaximumOnDemandCapacityUnits": 12,
"MaximumCoreCapacityUnits": 15
}
}

my expectation was:
12 core on-demand, 3 core spot
11 spot task nodes
1 master node

But my boto version gives exception.

Expected Behavior

it shouldn't throw validation exception

Current Behavior

it is throwing
botocore.exceptions.ClientError: An error occurred (ValidationException) when calling the RunJobFlow operation: Invalid configuration for managed scaling. If you select On-Demand market type for core nodes in a cluster with instance groups, MaximumCoreCapacityUnits must be less than or equal to MaximumOnDemandCapacityUnits.

Reproduction Steps

same as description

Possible Solution

same as description

Additional Information/Context

No response

SDK version used

1.18.59

Environment details (OS name and version, etc.)

amazon linux

@Pram098 Pram098 added bug This issue is a confirmed bug. needs-triage This issue or PR still needs to be triaged. labels Dec 1, 2023
@tim-finnigan tim-finnigan self-assigned this Dec 4, 2023
@tim-finnigan
Copy link
Contributor

Hi @Pram098 thanks for reaching out. The version 1.18.59 is quite old - the latest version of boto3/botocore is 1.33.7. (Here is the CHANGELOG for reference.)

Can you try updating to a more recent version to see if that resolves the issue?

@tim-finnigan tim-finnigan added service-api This issue is caused by the service API, not the SDK implementation. response-requested Waiting on additional information or feedback. emr and removed bug This issue is a confirmed bug. needs-triage This issue or PR still needs to be triaged. labels Dec 4, 2023
@Pram098
Copy link
Author

Pram098 commented Dec 5, 2023

I checked again, i noticed that for Instance Fleet there isn't any problem but Instance Group there is restriction by AWS, i guess it's good to close it.

@Pram098 Pram098 closed this as completed Dec 5, 2023
Copy link

github-actions bot commented Dec 5, 2023

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
emr response-requested Waiting on additional information or feedback. service-api This issue is caused by the service API, not the SDK implementation.
Projects
None yet
Development

No branches or pull requests

2 participants