[
https://issues.apache.org/jira/browse/FLINK-12152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16816103#comment-16816103
]
Paul Lin edited comment on FLINK-12152 at 4/12/19 9:00 AM:
-----------------------------------------------------------
[~yanghua] Would you mind clarifying further about under what condition does
this error happen? We also encounter Akka timeout when a job falls into an
erroneous state after some operation like rescale, it seems like some control
thread crashes but the task thread is not affected. Thanks!
was (Author: paul lin):
[~yanghua] Would you mind clarifying further about under what condition does
this error happen? We also encounter Akka timeout when a job falls into an
erroneous state after some operation like rescale, it seems like some control
thread crashes but the task thread is not affected.
> 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)
