You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2021/01/21 16:48:01 UTC
[jira] [Updated] (FLINK-10498) Decouple ExecutionGraph from
JobMaster
[ https://issues.apache.org/jira/browse/FLINK-10498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann updated FLINK-10498:
----------------------------------
Parent: (was: FLINK-10407)
Issue Type: New Feature (was: Sub-task)
> Decouple ExecutionGraph from JobMaster
> --------------------------------------
>
> Key: FLINK-10498
> URL: https://issues.apache.org/jira/browse/FLINK-10498
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / Coordination
> Affects Versions: 1.7.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Major
>
> With declarative resource management we want to react to the set of available resources. Thus, we need a component which is responsible for scaling the {{ExecutionGraph}} accordingly. In order to better do this and separate concerns, it is beneficial to introduce a {{Scheduler/ExecutionGraphDriver}} component which is in charge of the {{ExecutionGraph}}. This component owns the {{ExecutionGraph}} and is allowed to modify it. In the first version, this component will simply accommodate all the existing logic of the {{JobMaster}} and the respective {{JobMaster}} methods are forwarded to this component.
> This new component should not change the existing behaviour of Flink.
> Later this component will be in charge of announcing the required resources, deciding when to rescale and executing the rescaling operation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)