[
https://issues.apache.org/jira/browse/FLINK-14435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17195285#comment-17195285
]
lining commented on FLINK-14435:
--------------------------------
The previous configuration doesn't fully reflect the memory model of the task
manager. If the user chooses to configure the task manager's total memory, he
doesn't know how Flink allocates memory to heap/native/direct memory
internally. But if the user chooses to specify each part and the total
explicitly, then there's a possibility that the sum up of the part doesn't
match to the whole, then the job won't be started normally.
> Add TaskManageResourceInfo which match the memory compositions of taskmanager
> -----------------------------------------------------------------------------
>
> Key: FLINK-14435
> URL: https://issues.apache.org/jira/browse/FLINK-14435
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / REST
> Reporter: lining
> Assignee: Matthias
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.0
>
>
> * information from TaskExecutorResourceSpec in flip-49, add it to
> TaskExecutorRegistration.
> {code:json}
> public class TaskManagerResourceInfo {
> private final double cpuCores;
> private final long frameworkHeap;
> private final long frameworkOffHeap;
> private final long taskHeap;
> private final long taskOffHeap;
> private final long shuffleMemory;
> private final long managedMemory;
> private final long jvmMetaSpace;
> private final long jvmOverhead;
> private final long totalProcessMemory;
> }{code}
> * url: /taskmanagers/:taskmanagerid
> * response: add
> {code:java}
> resource: {
> cpuCores: 4,
> frameworkHeap: 134217728,
> frameworkOffHeap: 134217728,
> taskHeap: 181193928,
> taskOffHeap: 0,
> shuffleMemory: 33554432,
> managedMemory: 322122552,
> jvmMetaSpace: 134217728,
> jvmOverhead: 134217728,
> totalProcessMemory: 1073741824
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)