Dont use TaskInstance in CeleryExecutor.trigger_tasks#16248
Merged
Conversation
ashb
approved these changes
Jun 7, 2021
Contributor
|
The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease. |
kaxil
approved these changes
Jun 10, 2021
Contributor
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions. |
Member
|
ping @mik-laj |
Member
Author
|
Updated |
potiuk
approved these changes
Jul 26, 2021
nathadfield
pushed a commit
to king/airflow
that referenced
this pull request
Jul 29, 2021
* Dont use TaskInstance in CeleryExecutor.trigger_tasks * fixup! Merge branch 'main' into celery-multiprocessing-2
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We don't use this object so we don't need to send it.
Sending TI by multiprocessing sometimes fails because TaskInstance is not always properly serialized
Additionally, we have wrong typehint/variable names.
self.queued_taskscontainsOrderedDict[TaskInstanceKey, QueuedTaskInstanceType]objects whereQueuedTaskInstanceTypeis defined asTuple[CommandType, int, Optional[str], TaskInstance].airflow/airflow/executors/base_executor.py
Line 63 in 29409ac
airflow/airflow/executors/base_executor.py
Line 42 in 29409ac
airflow/airflow/executors/base_executor.py
Line 164 in 29409ac
Unfortunately, we were reading the values and writing them to the variable
simple_ti, but it's not valid. It should beti.airflow/airflow/executors/celery_executor.py
Line 252 in 29409ac
airflow/airflow/executors/celery_executor.py
Line 257 in 29409ac
I also confirmed it via the ipdb.
I tested it in my E2E environment: mik-laj/airflow-testing-example#2
Supersede: #16231
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.