[jira] [Comment Edited] (AIRFLOW-5328) EmrCreateJobFlowOperator success when EMR isn't ready

["Junyoung Park (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AIRFLOW-5328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16920155#comment-16920155 ] 

Junyoung Park edited comment on AIRFLOW-5328 at 8/31/19 3:58 PM:
-----------------------------------------------------------------

You can check the status of the cluster through emr_job_flow_sensor. 
In the current version, the EmrCreateJobFlowOperator only performs create_job_flow.


was (Author: swalloow):
You can check the status of the cluster through emr_job_flow_sensor.

In the current version, the EmrCreateJobFlowOperator only performs create_job_flow.

> EmrCreateJobFlowOperator success when EMR isn't ready
> -----------------------------------------------------
>
>                 Key: AIRFLOW-5328
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-5328
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: aws, operators
>    Affects Versions: 1.10.4
>            Reporter: Elad
>            Priority: Major
>
> EmrCreateJobFlowOperator returns almost instantly.
> It shouldn't return until the Emr cluster id ready.
> It doesn't make sense to submit tasks to EMR when the cluster isn't ready.
> Currently, tasks are submitted and waiting until the cluster will finish its initialization. 
> This can be checked with Waiter:
> [https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/emr.html]
> something like:
> {code:java}
> waiter = client.get_waiter('cluster_running').wait(ClusterId=response['JobFlowId'], WaiterConfig={'Delay': 32, 'MaxAttempts': 60}){code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)