Blind-Watchmaker commented on issue #21605:
URL: https://github.com/apache/airflow/issues/21605#issuecomment-1561276846
I'm also experiencing this problem while using `dbt` in Airflow:
Airflow v2.5.0
Kubernetes: 1.24.10 (Azure Kubernetes Service)
`apache-airflow-providers-cncf-kubernetes` 7.0.0
```
[2023-05-24, 14:02:49 UTC] {pod_manager.py:367} INFO -
[2m2023-05-24T13:57:48.744628Z[0m [[32m[1minfo [0m] [1m[0m13:57:48
105 of 105 START sql table model tap_mongodb.mart_name_here ..................
[RUN][0m [36mcmd_type[0m=[35mcommand[0m [36mname[0m=[35mdbt-***[0m
[36mstdio[0m=[35mstderr[0m
[2023-05-24, 14:07:49 UTC] {pod_manager.py:438} ERROR - Error parsing
timestamp (no timestamp in message ''). Will continue execution but won't
update timestamp
```
In this case, we're at a step in the execution process that could take a
long time and you can see that the error occurs exactly 5 minutes after the
previous line got executed. There isn't an empty log line in the log that
follows. My pipeline was working before when I was dealing with a smaller
dataset because the build time of this step was small enough, but I think there
might be some kind of KubernetesPodOperator related timeout at play here.
@potiuk/anyone else: Any ideas on Airflow variables I could play around with
to test this hypothesis?
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
