[
https://issues.apache.org/jira/browse/FLINK-10498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16642914#comment-16642914
]
Till Rohrmann commented on FLINK-10498:
---------------------------------------
It is somewhat related but not entirely. The {{ExecutionGraphDriver}} will use
the {{Scheduler}} internally to do the scheduling work. But it needs to do a
bit more than the scheduler in the long run. For example, it should be able to
decide on the actual parallelism of the job and when to scale up/down.
> Decouple ExecutionGraph from JobMaster
> --------------------------------------
>
> Key: FLINK-10498
> URL: https://issues.apache.org/jira/browse/FLINK-10498
> Project: Flink
> Issue Type: Sub-task
> Components: Distributed Coordination
> Affects Versions: 1.7.0
> Reporter: Till Rohrmann
> Priority: Major
> Fix For: 1.7.0
>
>
> 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
(v7.6.3#76005)
