You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Aizhamal Nurmamat kyzy (JIRA)" <ji...@apache.org> on 2019/05/18 02:56:00 UTC
[jira] [Updated] (AIRFLOW-4412) PodLauncher drops log lines printed
by the pod
[ https://issues.apache.org/jira/browse/AIRFLOW-4412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aizhamal Nurmamat kyzy updated AIRFLOW-4412:
--------------------------------------------
Component/s: (was: kubernetes)
operators
> PodLauncher drops log lines printed by the pod
> ----------------------------------------------
>
> Key: AIRFLOW-4412
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4412
> Project: Apache Airflow
> Issue Type: Bug
> Components: operators
> Affects Versions: 1.10.3
> Reporter: Ondrej Holecek
> Priority: Major
>
> When PodLauncher starts a pod, it is checking the pod status by
> pooling read_pod() method in 1s intervals until the pod state != QUEUE.
> After the pod starts, it tails the pod logs until the pod finishes. Due
> to the 1s pooling interval, there could be up to 1s delay between the
> real pod startup and the log tailing, and due to "tail_lines=10" all the
> lines above those last 10 logged within the 1s interval would be lost.
>
> The lines read from the stream returned by read_namespaced_pod_log()
> should be converted to string and right-stripped, since they contain
> '\n' character at the end.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)