Uh oh!
There was an error while loading. Please reload this page.
Move TaskInstance heartbeat directly on to TI row, not on Job row - #43599
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
This is part of the work for AIP-72 epic, but is done as a separate PR for ease of review. This PR byitself doesn't remove the LocalTaskJob row (that will happen in a future PR when the exeuction code is moved over to live in the TaskSDK) but this paves the way for it. The reason we are making this change is: - Having a separate row for tracking TI heartbeat is not really buying us much - With the addition of TaskInstanceHistory we don't need _another_ separate record of when/where TIs were run - It simplifies things (one less join in finding zombies) - Makes zombie tracking eaiser -- it is now just on the TI state, not the combination of TI and Job state.
32b90a5 to
6b17040CompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
jscheffl
left a comment
There was a problem hiding this comment.
Never noticed this structure and even w/o AIP-72 this seems to be odd. Good that you move it.
df23756 to
e180588CompareFollow-up of apache#43599, specifically https://github.com/apache/airflow/pull/43599/files#r1826351853 from @dstandish.
…ache#43599) This is part of the work for AIP-72 epic, but is done as a separate PR for ease of review. This PR by itself doesn't remove the LocalTaskJob row (that will happen in a future PR when the execution code is moved over to live in the TaskSDK) but this paves the way for it. The reason we are making this change is: - Having a separate row for tracking TI heartbeat is not really buying us much - With the addition of TaskInstanceHistory we don't need _another_ separate record of when/where TIs were run - It simplifies things (one less join in finding zombies) - Makes zombie tracking easier -- it is now just on the TI state, not the combination of TI and Job state.
This is part of the work for AIP-72 epic, but is done as a separate PR for
ease of review.
This PR byitself doesn't remove the LocalTaskJob row (that will happen in a
future PR when the exeuction code is moved over to live in the TaskSDK) but
this paves the way for it. The reason we are making this change is:
record of when/where TIs were run
combination of TI and Job state.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an 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 a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.