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

Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2019/05/27 08:48:00 UTC

[jira] [Resolved] (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:all-tabpanel ]

Till Rohrmann resolved FLINK-12152.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.9.0

Fixed via 4f558e4f225195fefe61718ef09b989f395987ba

> 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
>              Labels: pull-request-available
>             Fix For: 1.9.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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)