Closed gkiel closed 9 months ago
@gkiel this looks like an issue on the EMR API. I'll reach out to the EMR team and ask for clarification.
In case they ask for a requestID for analysis, can you provide a requestID of a runJobFlow
call?
@gkiel The EMR team replied saying the default for keepJobFlowAliveWhenNoSteps is not true, the documentation is incorrect. They'll fix the documentation.
Sounds good, thanks for the update!
I'll move this to the cross-SDK
repository to increase visibility to the other SDKs.
I'll also mark this to auto close soon, since there's no action pending from the SDK team, but let us know if you have any other question.
P99705632
Describe the bug
When creating an EMR cluster via runJobFlowRequest and providing an auto termination policy and not specifying any value for keepJobFlowAliveWhenNoSteps in the JobFlowInstancesConfig, the cluster will terminate once all steps have completed rather than waiting for the time specified in the auto termination policy.
Expected Behavior
I expected the EMR cluster to respect the auto termination policy by default since the documentation says that the default for keepJobFlowAliveWhenNoSteps is true: [https://sdk.amazonaws.com/java/api/latest/software/amazon/awssdk/services/emr/model/JobFlowInstancesConfig.html#keepJobFlowAliveWhenNoSteps()](https://sdk.amazonaws.com/java/api/latest/software/amazon/awssdk/services/emr/model/JobFlowInstancesConfig.html#keepJobFlowAliveWhenNoSteps())
Current Behavior
The EMR cluster shut down once all steps completed
Reproduction Steps
Possible Solution
No response
Additional Information/Context
Adding
.keepJobFlowAliveWhenNoSteps(true)
to the JobFlowInstancesConfig in the above snippet results in the EMR cluster respecting the auto termination policyAWS Java SDK version used
2.20.140
JDK version used
OpenJDK Runtime Environment Temurin-17.0.4.1+1 (build 17.0.4.1+1)
Operating System and version
MacOS Ventura 13.5