You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2020/01/16 15:51:00 UTC

[jira] [Resolved] (FLINK-15598) Memory accuracy loss in YarnClusterDescriptor may lead to deployment failure.

     [ https://issues.apache.org/jira/browse/FLINK-15598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann resolved FLINK-15598.
-----------------------------------
    Resolution: Fixed

Fixed via

master:
7acc0e6e08e20dc4e7b0cb1b3218c4049c57bf67
12f7873db54cfbc5bf853d66ccd4093f9b749c9a

1.10.0:
7b6aa1a63f45742557efc5d0bef2db40ebcc683d
91d96abe5f42bd088a326870b4885d79611fccb5

> Memory accuracy loss in YarnClusterDescriptor may lead to deployment failure.
> -----------------------------------------------------------------------------
>
>                 Key: FLINK-15598
>                 URL: https://issues.apache.org/jira/browse/FLINK-15598
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / YARN
>            Reporter: Xintong Song
>            Assignee: Xintong Song
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently, YarnClusterDescriptor parses/derives TM process memory size from configuration, store it in ClusterSpecification and validate ClusterSpecification, then overwrite the memory size back to configuration.
> This logic is unnecessary. The memory validation is already covered by creating TaskExecutorResourceSpec from configuration in TaskExecutorResourceUtils.
> Moreover, the memory size is stored in MB in ClusterSpecification. The accuracy loss may lead to memory validation failure, which prevent the cluster from being deployed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)