[
https://issues.apache.org/jira/browse/FLINK-12152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827049#comment-16827049
]
vinoyang commented on FLINK-12152:
----------------------------------
[~till.rohrmann] Sorry, It seems I did not describe my answer clearly. I mean
we try to view the jobmanager's log from web UI. But we can not open the whole
web page. You know, first, we should open the overview page then click the
"JobManager" menu. At last, we need to click the "Log" tab.
The behavior of scheduling is viewed from Yarn web console.
> 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)
