SetKeepJobFlowAliveWhenNoSteps
You can use the SetKeepJobFlowAliveWhenNoSteps
to configure a cluster (job flow) to terminate after the step execution, i.e., all your
steps are executed. If you want a transient cluster that shuts down after the last of the current executing steps are completed,
you can configure SetKeepJobFlowAliveWhenNoSteps
to false. If you want a long running cluster, configure SetKeepJobFlowAliveWhenNoSteps
to true.
For more information, see Managing Cluster Termination in the Amazon EMR Management Guide.
Request Syntax
{
"JobFlowIds": [ "string
" ],
"KeepJobFlowAliveWhenNoSteps": boolean
}
Request Parameters
For information about the parameters that are common to all actions, see Common Parameters.
The request accepts the following data in JSON format.
- JobFlowIds
-
A list of strings that uniquely identify the clusters to protect. This identifier is returned by RunJobFlow and can also be obtained from DescribeJobFlows.
Type: Array of strings
Length Constraints: Minimum length of 0. Maximum length of 10280.
Pattern:
[\u0020-\uD7FF\uE000-\uFFFD\uD800\uDC00-\uDBFF\uDFFF\r\n\t]*
Required: Yes
- KeepJobFlowAliveWhenNoSteps
-
A Boolean that indicates whether to terminate the cluster after all steps are executed.
Type: Boolean
Required: Yes
Response Elements
If the action is successful, the service sends back an HTTP 200 response with an empty HTTP body.
Errors
For information about the errors that are common to all actions, see Common Errors.
- InternalServerError
-
Indicates that an error occurred while processing the request and that the request was not completed.
HTTP Status Code: 400
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following: