nuclearpinguin commented on a change in pull request #6961: [AIRFLOW-XXX] Add task execution process on Celery Execution diagram URL: https://github.com/apache/airflow/pull/6961#discussion_r361938672
########## File path: docs/executor/celery.rst ########## @@ -143,3 +143,38 @@ The components communicate with each other in many places * [9] **Scheduler** --> **DAG files** - Reveal the DAG structure and execute the tasks * [10] **Scheduler** --> **Celery's result backend** - Gets information about the status of completed tasks * [11] **Scheduler** --> **Celery's broker** - Put the commands to be executed + +Task execution process +---------------------- + +.. figure:: ../img/run_task_on_celery_executor.png + :scale: 50 % + + Sequence diagram - task execution process + +Initially, two processes are running: + +- SchedulerProcess - process the tasks and run using CeleryExecutor +- WorkerProcess - observes the queue waiting for new tasks to appear +- WorkerChildProcess - waits for new tasks + +Two databases are also available: + +- QueueBroker +- ResultBackend + +During this process, two 2 process are created: Review comment: ```suggestion During this process, two process are created: ``` ? ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
