AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.
KeepJobFlowAliveWhenNoStepsparameter is set to
TRUE, the job flow will transition to the WAITING state rather than shutting down once the steps have completed.
For additional protection, you can set the JobFlowInstancesConfig
TRUE to lock the job flow and prevent it from being terminated
by API call, user intervention, or in the event of a job flow error.
A maximum of 256 steps are allowed in each job flow.
If your job flow is long-running (such as a Hive data warehouse) or complex, you may require more than 256 steps to process your data. You can bypass the 256-step limitation in various ways, including using the SSH shell to connect to the master node and submitting queries directly to the software running on the master node, such as Hive and Hadoop. For more information on how to do this, go to Add More than 256 Steps to a Job Flow in the Amazon Elastic MapReduce Developer's Guide.
For long running job flows, we recommend that you periodically store your results.
Version: (assembly version)
public virtual RunJobFlowResponse RunJobFlow( RunJobFlowRequest request )
Container for the necessary parameters to execute the RunJobFlow service method.
|InternalServerErrorException||Indicates that an error occurred while processing the request and that the request was not completed.|
Supported in: 4.5, 4.0, 3.5