[jira] [Resolved] (KUDU-3344) Master could do some garbage collection work in CatalogManagerBgTasks thread

["Alexey Serbin (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KUDU-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Serbin resolved KUDU-3344.
---------------------------------
    Fix Version/s: 1.17.0
       Resolution: Fixed

> Master could do some garbage collection work in CatalogManagerBgTasks thread
> ----------------------------------------------------------------------------
>
>                 Key: KUDU-3344
>                 URL: https://issues.apache.org/jira/browse/KUDU-3344
>             Project: Kudu
>          Issue Type: Improvement
>          Components: master
>            Reporter: YifanZhang
>            Priority: Minor
>             Fix For: 1.17.0
>
>
> Kudu master now reserve all tables/tablets' metadata in memory and disks, deleted tables and tablets were marked REMOVED/DELETED/REPLACED state but not really deleted. This could lead to huge memory usage as described in KUDU-3097.  
> I think it's a good idea to cleanup them in the CatalogManagerBgTasks thread. But because the data deletion tasks are done asynchronously by tablet servers, it is uncertain when metadata can be safely deleted.
> Besides, we could also cleanup dead tablet servers from master's in-memory map in this thread, as I mentioned in KUDU-2915.



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