[
https://issues.apache.org/jira/browse/FLINK-12152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16826150#comment-16826150
]
vinoyang commented on FLINK-12152:
----------------------------------
[~till.rohrmann] We tried to view JobManager's log from Flink web UI. It seems
the JobMaster is scheduling executions and sometimes it may fail then restart
and repeat this cycle. Our total parallelism is very large in this scene.
> 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)