You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Josh YEH (Jira)" <ji...@apache.org> on 2019/09/02 19:42:00 UTC
[jira] [Commented] (FLINK-13685) YARN deployment hangs when
requested container is above the maximum vcore size
[ https://issues.apache.org/jira/browse/FLINK-13685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16921030#comment-16921030 ]
Josh YEH commented on FLINK-13685:
----------------------------------
Hi [~bamrabi] [~gyfora] [~Tison] [~fly_in_gis],
I submitted my first [PR|[https://github.com/apache/flink/pull/9587]]. Please feel free to review. Thank you for your time!
Josh
> YARN deployment hangs when requested container is above the maximum vcore size
> ------------------------------------------------------------------------------
>
> Key: FLINK-13685
> URL: https://issues.apache.org/jira/browse/FLINK-13685
> Project: Flink
> Issue Type: New Feature
> Components: Deployment / YARN
> Affects Versions: 1.8.1
> Reporter: Gyula Fora
> Assignee: Josh YEH
> Priority: Major
>
> When deploying on YARN flink explicitly checks whether the requested container vcores is smaller than yarn.nodemanager.resource.cpu-vcores.
> Unfortunately this doesn't guarantee that the request can be fulfilled if yarn.scheduler.maximum-allocation-vcores is set to a lower number.
> In these cases flink will just keep trying to request a container but will never succeed.
>
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)