[jira] [Updated] (FLINK-13984) Separate on-heap and off-heap managed memory pools
[
https://issues.apache.org/jira/browse/FLINK-13984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Zagrebin updated FLINK-13984:
Fix Version/s: 1.10.0
> Separate on-heap and off-heap managed memory pools
> --
>
> Key: FLINK-13984
> URL: https://issues.apache.org/jira/browse/FLINK-13984
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Task
>Reporter: Xintong Song
>Assignee: Andrey Zagrebin
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> * Update {{MemoryManager}} to have two separated pools.
> * Extend {{MemoryManager}} interfaces to specify which pool to allocate
> memory from.
> Implement this step in common code paths for the legacy / new mode. For the
> legacy mode, depending to the configured memory type, we can set one of the
> two pools to the managed memory size and always allocate from this pool,
> leaving the other pool empty.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-13984) Separate on-heap and off-heap managed memory pools
[
https://issues.apache.org/jira/browse/FLINK-13984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-13984:
---
Labels: pull-request-available (was: )
> Separate on-heap and off-heap managed memory pools
> --
>
> Key: FLINK-13984
> URL: https://issues.apache.org/jira/browse/FLINK-13984
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Task
>Reporter: Xintong Song
>Assignee: Andrey Zagrebin
>Priority: Major
> Labels: pull-request-available
>
> * Update {{MemoryManager}} to have two separated pools.
> * Extend {{MemoryManager}} interfaces to specify which pool to allocate
> memory from.
> Implement this step in common code paths for the legacy / new mode. For the
> legacy mode, depending to the configured memory type, we can set one of the
> two pools to the managed memory size and always allocate from this pool,
> leaving the other pool empty.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-13984) Separate on-heap and off-heap managed memory pools
[
https://issues.apache.org/jira/browse/FLINK-13984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Zagrebin updated FLINK-13984:
Component/s: (was: Runtime / Coordination)
Runtime / Task
> Separate on-heap and off-heap managed memory pools
> --
>
> Key: FLINK-13984
> URL: https://issues.apache.org/jira/browse/FLINK-13984
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Task
>Reporter: Xintong Song
>Assignee: Andrey Zagrebin
>Priority: Major
>
> * Update {{MemoryManager}} to have two separated pools.
> * Extend {{MemoryManager}} interfaces to specify which pool to allocate
> memory from.
> Implement this step in common code paths for the legacy / new mode. For the
> legacy mode, depending to the configured memory type, we can set one of the
> two pools to the managed memory size and always allocate from this pool,
> leaving the other pool empty.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-13984) Separate on-heap and off-heap managed memory pools
[
https://issues.apache.org/jira/browse/FLINK-13984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Metzger updated FLINK-13984:
---
Component/s: Runtime / Coordination
> Separate on-heap and off-heap managed memory pools
> --
>
> Key: FLINK-13984
> URL: https://issues.apache.org/jira/browse/FLINK-13984
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
>Reporter: Xintong Song
>Assignee: Andrey Zagrebin
>Priority: Major
>
> * Update {{MemoryManager}} to have two separated pools.
> * Extend {{MemoryManager}} interfaces to specify which pool to allocate
> memory from.
> Implement this step in common code paths for the legacy / new mode. For the
> legacy mode, depending to the configured memory type, we can set one of the
> two pools to the managed memory size and always allocate from this pool,
> leaving the other pool empty.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-13984) Separate on-heap and off-heap managed memory pools
[
https://issues.apache.org/jira/browse/FLINK-13984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xintong Song updated FLINK-13984:
-
Description:
* Update {{MemoryManager}} to have two separated pools.
* Extend {{MemoryManager}} interfaces to specify which pool to allocate memory
from.
Implement this step in common code paths for the legacy / new mode. For the
legacy mode, depending to the configured memory type, we can set one of the two
pools to the managed memory size and always allocate from this pool, leaving
the other pool empty.
> Separate on-heap and off-heap managed memory pools
> --
>
> Key: FLINK-13984
> URL: https://issues.apache.org/jira/browse/FLINK-13984
> Project: Flink
> Issue Type: Sub-task
>Reporter: Xintong Song
>Priority: Major
>
> * Update {{MemoryManager}} to have two separated pools.
> * Extend {{MemoryManager}} interfaces to specify which pool to allocate
> memory from.
> Implement this step in common code paths for the legacy / new mode. For the
> legacy mode, depending to the configured memory type, we can set one of the
> two pools to the managed memory size and always allocate from this pool,
> leaving the other pool empty.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
