climate_ref_celery.executor
#
Executor for running diagnostics asynchronously using Celery
CeleryExecutor
#
Bases: Executor
Run a diagnostic asynchronously
Celery is an asynchronous task queue/job queue based on distributed message passing. Celery uses a message broker to distribute tasks across a cluster of worker nodes. The worker nodes are responsible for executing the tasks. The message broker used in this case is Redis. The worker node may be running on the same machine as the client or on a different machine, either natively or via a docker container.
We cannot resume tasks that are in progress if the process terminates. That should be possible tracking some additional state in the database.
Source code in packages/climate-ref-celery/src/climate_ref_celery/executor.py
21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 | |
join(timeout)
#
Wait for all executions to finish
This will block until all executions have finished running, and display a progress bar while waiting.
Any tasks still running after the timeout will continue to run in the background.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
timeout
|
float
|
Maximum time to wait in seconds before raising a TimeoutError |
required |
Raises:
| Type | Description |
|---|---|
TimeoutError
|
If all executions aren't completed within the specified timeout |
Source code in packages/climate-ref-celery/src/climate_ref_celery/executor.py
run(definition, execution=None)
#
Run a diagnostic calculation
This will queue the diagnostic to be run by a Celery worker.
The executions will be stored in the database when the task completes if execution
is specified.
No result will be returned from this function.
Instead, you can periodically check the status of the task in the database.
Tasks may not execute immediately if the correct workers are not available. The task will be queued and executed when a worker becomes available.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
definition
|
ExecutionDefinition
|
A description of the information needed for this execution of the diagnostic This includes relative paths to the data files, which will be converted to absolute paths when being executed |
required |
execution
|
Execution | None
|
Result of the diagnostic execution This is a database object that contains the executions of the execution. If provided, it will be updated with the executions of the execution. This may happen asynchronously, so the executions may not be immediately available. |
None
|