Airflow task glam-dev .scalar_percentiles failed on 2022-12-08 & 2022-12-13
Categories
(Data Platform and Tools :: General, defect, P4)
Tracking
(Not tracked)
People
(Reporter: kik, Assigned: kik)
Details
(Whiteboard: [airflow-triage])
Airflow task glam-dev .scalar_percentiles* failed to complete on 2022-12-13
It appears glam-dev
DAG has been stuck since 2022-12-13 this appears to be due to scalar_percentiles
being marked as skipped and resulting in the DAG never being marked as successful. What is unclear is why scalar_percentiles
was marked as skipped since the previous task according to the logs has exited with status code 0 (success) and I was unable to locate anything in the code indicating this to be expected behaviour.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
After attempting to re-run the task, we see the following error:
[2023-01-09, 11:05:15 UTC] {{pod_manager.py:226}} INFO - Found versions: []
[2023-01-09, 11:05:15 UTC] {{pod_manager.py:226}} INFO - Source table empty
Which seems to come from here:
https://github.com/mozilla/bigquery-etl/blob/589e9192e7a98b59dcdb814a457575e24b5bec4b/script/glam/run_scalar_agg_clustered_query.py#L50-L52
This results in status code 1 being returned and the pod exits as failed. This status is propagated back to Airflow and therefore the job fails.
We see the same behaviour for run date: 2022-12-08
.
In the meantime, marking the tasks in question as failed manually to verify that this fixes the scheduling issues for newer runs.
Assignee | ||
Comment 2•2 years ago
•
|
||
Oops, just noticed this DAG has no schedule and has to be run manually explaining why no recent runs exist. Correcting the bug title to reflect the issue more accurately.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 3•2 years ago
|
||
Marked as low priority as this does not appear to be a production DAG and is only run on-demand. I assume it is used for testing changes only.
Assignee | ||
Comment 4•2 years ago
|
||
:efilho, do we care about these failures? And since this is dev do you think we should just delete this bug ticket?
Assignee | ||
Comment 5•2 years ago
|
||
Eduardo confirmed this is fine. Marking this as INVALID and resolved.
Description
•