You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Zhu Zhu (Jira)" <ji...@apache.org> on 2022/06/24 07:27:00 UTC

[jira] [Closed] (FLINK-28133) Rework DefaultScheduler to directly deploy executions

     [ https://issues.apache.org/jira/browse/FLINK-28133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhu Zhu closed FLINK-28133.
---------------------------
    Resolution: Done

Done via c66101d518615ec2d6a36c829568583a6a5d93f9

> Rework DefaultScheduler to directly deploy executions
> -----------------------------------------------------
>
>                 Key: FLINK-28133
>                 URL: https://issues.apache.org/jira/browse/FLINK-28133
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Coordination
>            Reporter: Zhu Zhu
>            Assignee: Zhu Zhu
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.16.0
>
>
> Currently, the DefaultScheduler(base of AdaptiveBatchScheduler) can only perform ExecutionVertex level deployment. However, in this case, the scheduler is actually deploying the current execution attempt of the ExecutionVertex.
> Therefore, we need to rework the DefaultScheduler to directly deploy executions.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)