[
https://issues.apache.org/jira/browse/FLINK-12023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16803536#comment-16803536
]
vinoyang commented on FLINK-12023:
----------------------------------
[~RustedBones] I do not think it is valuable. Your deploy mode is YARN Flink
session. It allows running many jobs. I think we should not let a job
submitting change a TaskManager's memory setting. And this reverse control is
not reasonable. This belongs to the cluster management scope. What do you
think? [~till.rohrmann]
> Override TaskManager memory when submitting a Flink job
> -------------------------------------------------------
>
> Key: FLINK-12023
> URL: https://issues.apache.org/jira/browse/FLINK-12023
> Project: Flink
> Issue Type: Wish
> Components: Runtime / Configuration
> Reporter: Michel Davit
> Assignee: vinoyang
> Priority: Minor
>
> Currently a Flink session can only run Task managers of the same size.
> However, depending on the jar or even the program arguments, we can have more
> intensive job that other.
> In order to improve memory usage and avoid resource waste, It would be useful
> to have an option that overrides the default task manager memory setting when
> submitting a new job.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
