I did an experiment these two days.Insert thousands of batches of data into a table use global_sort.I found that the first query use 4800s JDBC memery is 14BG;when first finish i do the second query immediately use the same sql "select count(*) from sameTable". The result is second query take 3700s and the JDBC memery increase to 20GB,between first and second there is no other insertion and query.see the LRU debug log we can see like this:" Removed entry from InMemory lru cache :: hdfs://hacluster/user/hive/warehouse/carbon.store/ps/xx_17910/Fact/Part0/Segment_2497/2497_1547575104816.carbonindexmerge | org.apache.carbondata.core.cache.CarbonLRUCache.removeKey(CarbonLRUCache.java:163)2"may be the LRU cache is remove from memery,beside there is not another query.From these phenomena, it may be seen that there are several problems.1）is there has memory leaks for the 14GB ->20GB memery use.(i have jmap dump file)2）Can the logic of LRU be optimized? 3）Is it possible to concurrently load index Files to LRU Using thread pools
-- Sent from: http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
