You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "wangningito (Jira)" <ji...@apache.org> on 2020/05/28 11:39:00 UTC

[jira] [Updated] (KUDU-3097) master should delete table info if table deleted, instead of keeping them forever

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

wangningito updated KUDU-3097:
------------------------------
    Attachment: screenshot-1.png

> master should delete table info if table deleted, instead of keeping them forever
> ---------------------------------------------------------------------------------
>
>                 Key: KUDU-3097
>                 URL: https://issues.apache.org/jira/browse/KUDU-3097
>             Project: Kudu
>          Issue Type: New Feature
>            Reporter: wangningito
>            Assignee: wangningito
>            Priority: Major
>         Attachments: screenshot-1.png
>
>
> Recently I addressed a memory problem occurred by kudu master.
> Related info:
> Master memory report by system , 8.6g 
> Master memory report by kudu web page, 1g 
> The master keep running from 2018 to now, and still running.
> During two years, I create over 30000 tables and delete them for test requirement. And we keep only 20 tables running during those time. 
> I found the memory usage strange, so I tried to dump all the data of master via
> "kudu lcoal_replica dump rowset 000000000 ..."
> I found over 330k records  in the environment. And the records are just mark as deleted. 
> Guess this could cause be the burden for master, and some untracked memory.



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