Yahui Liu created CARBONDATA-4088:
-------------------------------------
Summary: 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
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)
