[
https://issues.apache.org/jira/browse/FLINK-19662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann closed FLINK-19662.
---------------------------------
Fix Version/s: 1.12.0
Resolution: Fixed
Fixed via
d2d7b20b452b90e51133f4ada6c2118a2cf92496
5abd3bfad778e1665560b4c8e7661efcb51b3486
0a51d85255b9c7480eb5e939d88e9ccc5e98af69
cdbce714ae5b575c07d6191c8f08951208f2f27c
2c8631a4eb7a247ce8fb4205f838e8c0f8019367
2eaee8344bdcab961799127c7e72d3f4abe75726
> Create or extend REST endpoint to expose memory configuration
> -------------------------------------------------------------
>
> Key: FLINK-19662
> URL: https://issues.apache.org/jira/browse/FLINK-19662
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Web Frontend
> Reporter: Matthias
> Assignee: Matthias
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.0
>
>
> We need to expose the memory configuration finally used within the
> JobManager. The effective configuration is calculated differently depending
> on the type of cluster (legacy vs containerized). The goal is to have the
> configuration being calculated only in one place. Therefore, we want to
> forward the information through environment variables similar to the approach
> already done for the TaskManager.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)