[
https://issues.apache.org/jira/browse/FLINK-12152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16821017#comment-16821017
]
Till Rohrmann commented on FLINK-12152:
---------------------------------------
[~Paul Lin] what behaviour do you observe? Do you observe that the job cannot
be cancelled/stopped after it has been rescaled? I might have a suspicion what
could have caused such a behaviour.
[~yanghua] I would also be interested to learn a bit more about the problem you
are seeing. Could you maybe share some logs with us? In general I agree that
the vcores per AM should be configurable.
> Make the vcore that Application Master used configurable for Flink on YARN
> --------------------------------------------------------------------------
>
> Key: FLINK-12152
> URL: https://issues.apache.org/jira/browse/FLINK-12152
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
> Reporter: vinoyang
> Assignee: vinoyang
> Priority: Major
>
> Now, for Flink on YARN deployment mode, each am's vcores is specified to 1
> (hard code).
> In some scene, we found many Akka timeout logs, the Flink web UI cannot be
> opened, but it is alive. I think there is no more threads resource to be used
> for am. So we suggest that make the vcores num of application master can be
> configurable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
