flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Till Rohrmann (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-10506) Introduce minimum, target and maximum parallelism to JobGraph
Date Mon, 04 Mar 2019 15:26:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-10506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783453#comment-16783453

Till Rohrmann commented on FLINK-10506:

Hi [~yanghua], this is a bit of tricky issue because we have to maintain the {{JobGraphs}}
backwards compatibility and hence should be careful when adding new fields. Therefore, I would
suggest to not start working on this issue. Or at least we should have a very detailed plan
how to solve this issue.

> 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
>            Assignee: vinoyang
>            Priority: Major
>             Fix For: 1.8.0
> 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

View raw message