You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yangze Guo (Jira)" <ji...@apache.org> on 2022/04/01 01:35:00 UTC

[jira] [Commented] (FLINK-25794) Memory pages in LazyMemorySegmentPool should be clear after they are released to MemoryManager

    [ https://issues.apache.org/jira/browse/FLINK-25794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17515657#comment-17515657 ] 

Yangze Guo commented on FLINK-25794:
------------------------------------

[~zjureel] Is this issue still valid? Shall we close it?

> Memory pages in LazyMemorySegmentPool should be clear after they are released to MemoryManager
> ----------------------------------------------------------------------------------------------
>
>                 Key: FLINK-25794
>                 URL: https://issues.apache.org/jira/browse/FLINK-25794
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / Runtime
>    Affects Versions: 1.11.6, 1.13.5, 1.14.3
>            Reporter: Shammon
>            Assignee: Shammon
>            Priority: Major
>              Labels: pull-request-available, stale-assigned
>
> `LazyMemorySegmentPool` manages memory segments cache for join, agg, sort and etc. operators. These segments in the cache will be released to `MemoryManager` after some specify operations such as join operator finishes to build data in `LazyMemorySegmentPool.cleanCache` method. But these segments are still in `LazyMemorySegmentPool.cachePages`, it may cause memory fault if the `MemoryManager` has deallocated these segments



--
This message was sent by Atlassian Jira
(v8.20.1#820001)