[
https://issues.apache.org/jira/browse/FLINK-12152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16822436#comment-16822436
]
Paul Lin edited comment on FLINK-12152 at 4/20/19 1:18 PM:
-----------------------------------------------------------
[~yanghua] Thanks a lot for the information. In my case, the job parallelism is
5, so the dispatch thread wouldn't have load issues. If the timeout happens
right after the job runs instead of when the job restarts in your case, we
might have different issues.
was (Author: paul lin):
[~yanghua] Thanks a lot for the information. In my case, the job parallelism is
5, so the dispatch thread wouldn't have load issues. I suspect our cases are
about the same problem but not the resources.
> 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)
