[
https://issues.apache.org/jira/browse/FLINK-19954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-19954:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Move execution deployment tracking logic from legacy EG code to SchedulerNG
> ---------------------------------------------------------------------------
>
> Key: FLINK-19954
> URL: https://issues.apache.org/jira/browse/FLINK-19954
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.12.0
> Reporter: Andrey Zagrebin
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> FLINK-17075 introduced the execution state reconciliation between TM and JM.
> The reconciliation requires tracking of the execution deployment state. The
> tracking logic was added to the legacy code of EG state handling which is
> partially inactive as discussed in FLINK-19927. The recent state handling
> logic resides in the new SchedulerNG, currently DefaultScheduler.
> We could reconsider how the execution tracking for reconciliation is
> integrated with the scheduling. I think the tracking logic could be moved
> from Execution#deploy and EG#notifyExecutionChange to either
> SchedulerNG#updateTaskExecutionState or DefaultScheduler#deployTaskSafe. The
> latter looks to me currently more natural. ExecutionVertexOperations.deploy
> could return submission future for deployment completion in
> ExecutionDeploymentTracker and Execution#getTerminalFuture to stop the
> tracking. This would be also easier to unit test.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
