[jira] [Created] (AIRFLOW-4393) Add retry logic when fetching pod status and/or logs in KubernetesPodOperator

["Olivier Van Goethem (JIRA)" <ji...@apache.org>]

Olivier Van Goethem created AIRFLOW-4393:
--------------------------------------------

             Summary: Add retry logic when fetching pod status and/or logs in KubernetesPodOperator
                 Key: AIRFLOW-4393
                 URL: https://issues.apache.org/jira/browse/AIRFLOW-4393
             Project: Apache Airflow
          Issue Type: Bug
            Reporter: Olivier Van Goethem


Over the last weeks we have observed 2 occasions where:
 * KubernetesPodOperator successfully launches the pod
 * KubernetesPodOperator then fails when attempting to check the pod status due to: 
{code:java}
NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f1329dc0cf8>: Failed to establish a new connection: [Errno 111] Connection refused',)
{code}

 * KubernetesPodOperator launches another pod
 * We know have 2 pods running in parallel

The cause for the 'Connection refused' is due to a transient network error. As such, the KubernetesPodOperator should attempt to retry checking the pod status/logs rather than failing the task.

Airflow is being run through GCP's Cloud Composer.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)