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/06/13 11:39:00 UTC
[jira] [Commented] (AIRFLOW-4594) Kubernetes watcher updating Task
state based on Pod state
[ https://issues.apache.org/jira/browse/AIRFLOW-4594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16862982#comment-16862982 ]
ASF GitHub Bot commented on AIRFLOW-4594:
-----------------------------------------
ramandumcs commented on pull request #5345: AIRFLOW-4594 Pod state might be different from task state. So don't c…
URL: https://github.com/apache/airflow/pull/5345
----------------------------------------------------------------
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
> Kubernetes watcher updating Task state based on Pod state
> ---------------------------------------------------------
>
> Key: AIRFLOW-4594
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4594
> Project: Apache Airflow
> Issue Type: Bug
> Components: executors
> Affects Versions: 1.10.1
> Reporter: raman
> Assignee: raman
> Priority: Major
>
> Currently KubernetesJobWatcher updates the task state based on the pod state inside
> process_status function. If it gets the pod state as failed it marks the task state to failed which is not the correct behaviour because task might move to retry state or reschedule state.
> Pod might be failed because of various reasons like machine/network issue, it might crash. But its state might not reflect the task state
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)