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/27 14:41:00 UTC
[jira] [Resolved] (FLINK-15763) Check or set necessary resource
configuration options to defaults for local execution ignoring FLIP-49
[ https://issues.apache.org/jira/browse/FLINK-15763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann resolved FLINK-15763.
-----------------------------------
Resolution: Fixed
Fixed via
master: 03c7274b9a9fbec2acbe86ba3289c7b9d460ea42
1.10.0: cd42cd0f7827c9b8e4112020eb6c1072945d7830
> Check or set necessary resource configuration options to defaults for local execution ignoring FLIP-49
> ------------------------------------------------------------------------------------------------------
>
> Key: FLINK-15763
> URL: https://issues.apache.org/jira/browse/FLINK-15763
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Task
> Reporter: Andrey Zagrebin
> Assignee: Andrey Zagrebin
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> FLIP-49 (FLINK-13980) calculates memory setup to start TM process. Atm, we reuse this logic to get necessary resource configuration options in running TM, although we do not need the full TaskExecutorResourceSpec which can be renamed to TaskExecutorProcessSpec.
> In case of local execution in mini cluster, the TM process is started outside of Flink framework and nothing is pre-calculated. It means that any configured process or Flink memory size can make no sense and can be ignored then to make things simpler and more explicit. Also the result of FLIP-49 calculation can contradict to the default values and other derived FLIP-49 memory components are not used by TM internally anyways. If some necessary options are not set, we can set them to reasonable defaults.
> The configuration options required for running TM, which are expected to be calculated and set before its start, are the following (with defaults for local execution):
> * cpu cores (potentially for FLIP-56, [FLINK-14187|https://jira.apache.org/jira/browse/FLINK-14187], default: Double.MAX_VALUE)
> * task heap memory (potentially for FLIP-56, [FLINK-14187|https://jira.apache.org/jira/browse/FLINK-14187], default: MemorySize.MAX_VALUE)
> * task off-heap memory (potentially for FLIP-56, [FLINK-14187|https://jira.apache.org/jira/browse/FLINK-14187], default: MemorySize.MAX_VALUE)
> * network memory (default: 64Mb)
> * managed memory (default: 128Mb)
> Additionally, we can refactor TM runner to not reuse current FLIP-49 computation but just check that the necessary options are set and create TaskExecutorResourceSpec which contains only them.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)