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
We currently have a notebook that executes other notebooks in parallel (number of notebooks depends on runtime parameters).
The current solution is to execute dbutils.notebooks.run within ThreadPoolExecutor. I'm worried that this might not make optimal use of Databricks cluster resources and would like to use native scheduling functionality.
In the example within this repo the JobsAPI is used to execute a dynamically generated job, which seems nice.
My question is the following: How can I
reduce the amount of output (for example, only log when status changes, only show job url once),
catch exceptions raised within the tasks.
I essentially want to execute the tasks in parallel, wait until all of them are either finished, cancelled or failed and then gather exceptions if any were raised and further deal with them in the caller notebook.
I am now using this bit of code in my caller notebook to run some tests:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We currently have a notebook that executes other notebooks in parallel (number of notebooks depends on runtime parameters).
The current solution is to execute
dbutils.notebooks.run
withinThreadPoolExecutor
. I'm worried that this might not make optimal use of Databricks cluster resources and would like to use native scheduling functionality.In the example within this repo the JobsAPI is used to execute a dynamically generated job, which seems nice.
My question is the following: How can I
I essentially want to execute the tasks in parallel, wait until all of them are either finished, cancelled or failed and then gather exceptions if any were raised and further deal with them in the caller notebook.
I am now using this bit of code in my caller notebook to run some tests:
The notebook that is called contains
Beta Was this translation helpful? Give feedback.
All reactions