You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/11/08 15:20:00 UTC
[jira] [Commented] (AIRFLOW-5312) KubernetesPodOperator hangs when
kubernetes API times out
[ https://issues.apache.org/jira/browse/AIRFLOW-5312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16970275#comment-16970275 ]
ASF GitHub Bot commented on AIRFLOW-5312:
-----------------------------------------
stale[bot] commented on pull request #5915: [AIRFLOW-5312] Fix timeout issue in pod launcher / KubernetesPodOperator
URL: https://github.com/apache/airflow/pull/5915
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> KubernetesPodOperator hangs when kubernetes API times out
> ---------------------------------------------------------
>
> Key: AIRFLOW-5312
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5312
> Project: Apache Airflow
> Issue Type: Bug
> Components: contrib
> Affects Versions: 1.10.4
> Reporter: Roland de Boo
> Assignee: Roland de Boo
> Priority: Major
>
> The KubernetesPodOperator launches a Pod in Kubernetes and then continues to watch its state and stream its logs. This is done via the Kubernetes Api. Not all calls to the Kubernetes Api have a timeout defined, so the operator will wait indefinitely for a response and therefore get stuck.
> This is the same issue as https://issues.apache.org/jira/browse/AIRFLOW-5282 but now in the KubernetesPodOperator.
> The solution is to add a timeout on all Api calls, and handle the errors (catching them, adding tenacity retrying where appropriate).
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)