You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gary Yao (JIRA)" <ji...@apache.org> on 2019/04/26 15:12:00 UTC
[jira] [Comment Edited] (FLINK-12126) Make relaxed rescaling
behaviour accessible in REST interface
[ https://issues.apache.org/jira/browse/FLINK-12126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827037#comment-16827037 ]
Gary Yao edited comment on FLINK-12126 at 4/26/19 3:11 PM:
-----------------------------------------------------------
[~jshs] Thanks for following up. I have created FLINK-12341 to track the efforts to re-enable the job rescaling.
was (Author: gjy):
[~jshs] Thanks for following up. I have created FLINK-12341
> 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)