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

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

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

Elad commented on AIRFLOW-5328:
-------------------------------

[~Swalloow] EmrJobFlowSensor doesn't have the functionality I'm after.

It asks for state of the JobFlow until it reaches a terminal state.

You use this sensor after submitted a Job to check for its progress.

I'm looking for a way to check the EMR cluster state regardless of a specific job.

Either by sensor or by EmrCreateJobFlowOperator not to return until the Cluster is ready.

 

I don't see the point by EmrCreateJobFlowOperator returning immediately then submit a Job and have that job hang because the cluster is on BOOTSTRAPPING. I want to submit jobs only when the cluster is ready.

> 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)