Reduce maptask transitions between WaitingForResources and CheckingSubtaskExecutions #4790
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.
Tracking issue
NA
Why are the changes needed?
In maptask, if any subtasks are in the
PhaseWaitingForResources
phase then the entire maptask task transitions to that phase. The issue is that thek8s-array
plugin uses a transition throughPhaseLaunch
to get back toPhaseCheckingSubtaskExecutions
here. This causes events to be sent to flyteadmin to satisfy the phase update. With this commit flyteadmin began processing phase reason updates in batches, which causes all reason updates to persist in a timeline. The continual transition betweenPhaseWaitingForResources
andPhaseCheckingSubtaskExecutions
causes a large amount of duplicated reasons in the time series.What changes were proposed in this pull request?
This PR proposed to treat
PhaseWaitingForResources
andPhaseCheckingSubtaskExecutions
the same so that events are only sent when subtask phases are updated rather than duplicate transitions between these maptask phases.How was this patch tested?
Locally.
Setup process
Screenshots
Check all the applicable boxes
Related PRs
NA
Docs link
NA