[
https://issues.apache.org/jira/browse/AIRFLOW-5328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16963655#comment-16963655
]
Juan Ramos Fuentes commented on AIRFLOW-5328:
---------------------------------------------
+1 for this! emr_job_flow_sensor will only succeed when the cluster reaches
TERMINATED status, which I don't think makes a lot of sense. Instead, the
sensor should succeed when the cluster is ready to accept steps (WAITING
status).
I really like [~ash]'s suggestion of adding a new flag to check for different
cluster status.
> EmrCreateJobFlowOperator success when EMR isn't ready
> -----------------------------------------------------
>
> Key: AIRFLOW-5328
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5328
> Project: Apache Airflow
> Issue Type: Improvement
> 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.4#803005)
