[
https://issues.apache.org/jira/browse/FLINK-12126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826890#comment-16826890
]
Joshua Schneider commented on FLINK-12126:
------------------------------------------
[~gjy] Thanks for the heads-up. This is not really a problem for us; we can
stay on a version that supports rescaling for the time being (or go the
savepoint route). Of course it would be great to have a fully working,
integrated rescaling story at some point. Is there an issue or document that
tracks these efforts?
> 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)
