cancel_steps
async
¶
cancel_steps(
*,
config_overrides: Optional[AsyncEMRClientConfig] = None,
cluster_id: Optional[XmlStringMaxLen256] = None,
step_ids: Optional[StepIdsList] = None,
step_cancellation_option: Optional[StepCancellationOption] = None,
) -> CancelStepsOutput
Cancels a pending step or steps in a running cluster. Available only in Amazon EMR versions 4.8.0 and later, excluding version 5.0.0. A maximum of 256 steps are allowed in each CancelSteps request. CancelSteps is idempotent but asynchronous; it does not guarantee that a step will be canceled, even if the request is successfully submitted. When you use Amazon EMR releases 5.28.0 and later, you can cancel steps that are in a PENDING or RUNNING state. In earlier versions of Amazon EMR, you can only cancel steps that are in a PENDING state.
Parameters:
-
cluster_id(Optional[XmlStringMaxLen256], default:None) –The
ClusterIDfor the specified steps that will be canceled. Use RunJobFlow and ListClusters to get ClusterIDs. -
step_ids(Optional[StepIdsList], default:None) –The list of
StepIDsto cancel. Use ListSteps to get steps and their states for the specified cluster. -
step_cancellation_option(Optional[StepCancellationOption], default:None) –The option to choose to cancel
RUNNINGsteps. By default, the value isSEND_INTERRUPT.
Raises:
-
InternalServerError–Indicates that an error occurred while processing the request and that the request was not completed.
-
InvalidRequestException–This exception occurs when there is something wrong with user input.
-
UnknownServiceError–The service returned an error code this client does not model.