[
https://issues.apache.org/jira/browse/KUDU-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17712196#comment-17712196
]
YifanZhang commented on KUDU-3463:
----------------------------------
[~weizisheng]This issue seems related to KUDU-3097 and KUDU-3344. The fix for
KUDU-3344 will be included in Kudu 1.17.0 release.
I think it's not a memory leak in the Kudu leader master. The reason is too
many table and tablet metadata are preserved in the memory. Maybe you can try
to pick the changes in KUDU-3344 and set
--enable_metadata_cleanup_for_deleted_tables_and_tablets=true for Kudu masters,
to see if the memory usage can be reduced.
> KuduMaster leader consumes too much memory
> ------------------------------------------
>
> Key: KUDU-3463
> URL: https://issues.apache.org/jira/browse/KUDU-3463
> Project: Kudu
> Issue Type: Bug
> Affects Versions: 1.12.0
> Reporter: Weizisheng
> Priority: Major
> Attachments: heap321.txt
>
>
> We rarely face a suspected memory leak on a cluster with 3-master and
> 4-tserver, 800 tables and 3000 tablets. Leader master consume 50GB memory
> while the other two only take one tenth of it ...
> From the last 5 days, leader's memory usage grows 3%+
> attachment pprof heap
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
