You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "vinoyang (JIRA)" <ji...@apache.org> on 2019/05/13 08:32:00 UTC

[jira] [Commented] (FLINK-12152) Make the vcore that Application Master used configurable for Flink on YARN

    [ https://issues.apache.org/jira/browse/FLINK-12152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838370#comment-16838370 ] 

vinoyang commented on FLINK-12152:
----------------------------------

What do you think about adding a config option to make the am's vcore configurable? [~till.rohrmann]

> 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)