You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/modules/demos/pages/airflow-scheduled-job.adoc
+59Lines changed: 59 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -129,6 +129,65 @@ asynchronously - and another to poll the running job to report on its status.
129
129
130
130
image::airflow-scheduled-job/airflow_11.png[]
131
131
132
+
== Patching Airflow to stress-test DAG parsing using relevant environment variables
133
+
134
+
The demo also created a third DAG in the ConfigMap, called `dag_factory.py`, which was not mounted to the cluster and therefore does not appear in the UI.
135
+
This DAG can be used to create a number of individual DAGs on-the-fly, thus allowing a certain degree of stress-testing of the DAG scan/register steps (the generated DAGs themselves are trivial and so this approach will not really increase the burden of DAG _parsing_).
136
+
To include this in the list of DAGs (without removing the existing ones), an extra volumeMount is needed, as shown below.
137
+
The patch also sets some environment variables that can be used to change the frequency of certain operations. The descriptions can be found here: https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html[window=_blank].
The scheduled job runs every minute and so an instance of it may be running while the scheduler is being re-started as a result of the patch, in which case that instance may fail.
189
+
====
190
+
132
191
== Summary
133
192
134
193
This demo showed how DAGs can be made available for Airflow, scheduled, run and then inspected with the Webserver UI.
0 commit comments