2 Answers
- Newest
- Most votes
- Most comments
0
Hi there!
Can you try using taskInstanceBidPrice
instead of spotBidPrice
?
I hope this helps.
0
Hi,
I can see from the current pipeline settings, that the “useOnDemandOnLastAttempt” is set to “true”. The parameter 'useOnDemandOnLastAttempt' is set to true by default. To avoid getting on demand instances used for EMR cluster, when Spot instances are not available you need to set this parameter to false. Also the maximum attempts for EMR cluster resource is defaulted to "1", you can also change the "maximumRetries" of EMR cluster to more than “1”. Currently you have "maximumRetries: 2” you can increase it to get the spot instances in other attempts.
Scenarios where the spot instances fail to launch
- Spot price is low than the minimum required Spot request fulfillment price.
- Limitation issue "EXCEEDED_SPOT_INSTANCE_COUNT_LIMIT (USER_ERROR)".
Relevant content
- asked a year ago
- asked 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
I set it as the following (using
coreInstanceBidPrice
andtaskInstanceBidPrice
), but still not working (it is still running on demand):