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 2020/04/24 10:15:00 UTC

[jira] [Closed] (FLINK-10506) Introduce minimum, target and maximum parallelism to JobGraph

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

Till Rohrmann closed FLINK-10506.
---------------------------------
    Resolution: Later

This issue is quite outdated and needs to be updated once the design for declarative resource management and the reactive mode has been accepted.

> Introduce minimum, target and maximum parallelism to JobGraph
> -------------------------------------------------------------
>
>                 Key: FLINK-10506
>                 URL: https://issues.apache.org/jira/browse/FLINK-10506
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Coordination
>    Affects Versions: 1.7.0
>            Reporter: Till Rohrmann
>            Priority: Major
>
> In order to run a job with a variable parallelism, one needs to be able to define the minimum and maximum parallelism for an operator as well as the current target value. In the first implementation, minimum could be 1 and maximum the max parallelism of the operator if no explicit parallelism has been specified for an operator. If a parallelism p has been specified (via setParallelism(p)), then minimum = maximum = p. The target value could be the command line parameter -p or the default parallelism.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)