[
https://issues.apache.org/jira/browse/FLINK-12126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825461#comment-16825461
]
Gary Yao commented on FLINK-12126:
----------------------------------
[~jshs] We are planning to temporarily remove the rescaling feature. Would that
be a problem for you? There is an ongoing thread on the user mailing list about
this:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/DISCUSS-Temporarily-remove-support-for-job-rescaling-via-CLI-action-quot-modify-quot-td27447.html
> Make relaxed rescaling behaviour accessible in REST interface
> -------------------------------------------------------------
>
> Key: FLINK-12126
> URL: https://issues.apache.org/jira/browse/FLINK-12126
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / REST
> Affects Versions: 1.7.2
> Reporter: Joshua Schneider
> Priority: Minor
>
> The REST handler for rescaling uses RescalingBehaviour.STRICT as a hard-coded
> parameter. This has the following consequences when a job is rescaled:
> * All operators are set to the new parallelism. If at least one operator's
> max parallelism is less than the new parallelism, the rescale operation is
> aborted.
> * Therefore, it is impossible to restrict the parallelism of a subset of
> operators (say, to one) in combination with rescaling.
> A different behaviour which fixes these issues, RescalingBehaviour.RELAXED,
> is already provided by the internal API. However, it appears to be unused.
> The REST interface should provide a parameter that selects the strategy.
> Alternatively, it could be a setting of the job.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
