[jira] [Commented] (CARBONDATA-4088) Drop metacache didn't clear some cache information which leads to memory leak

[Akash R Nilugal (Jira)]

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

Akash R Nilugal commented on CARBONDATA-4088:
---------------------------------------------

please handle [https://issues.apache.org/jira/browse/CARBONDATA-4098|https://issues.apache.org/jira/browse/CARBONDATA-4098]

> Drop metacache didn't clear some cache information which leads to memory leak
> -----------------------------------------------------------------------------
>
>                 Key: CARBONDATA-4088
>                 URL: https://issues.apache.org/jira/browse/CARBONDATA-4088
>             Project: CarbonData
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 2.1.0
>            Reporter: Yahui Liu
>            Priority: Minor
>          Time Spent: 6h
>  Remaining Estimate: 0h
>
> When there are two spark applications, one drop a table, some cache information of this table stay in another application and cannot be removed with any method like "Drop metacache" command. This leads to memory leak. With the passage of time, memory leak will also accumulate which finally leads to driver OOM. Following are the leak points: 1) tableModifiedTimeStore in CarbonFileMetastore; 2) segmentLockMap in BlockletDataMapIndexStore; 3) absoluteTableIdentifierByteMap in SegmentPropertiesAndSchemaHolder; 4) tableInfoMap in CarbonMetadata.

--
This message was sent by Atlassian Jira
(v8.3.4#803005)