You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "Balaji Varadarajan (Jira)" <ji...@apache.org> on 2020/06/04 08:08:00 UTC
[jira] [Commented] (HUDI-997) Debug possible memory leaks when
running tests in hudi-client
[ https://issues.apache.org/jira/browse/HUDI-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125667#comment-17125667 ]
Balaji Varadarajan commented on HUDI-997:
-----------------------------------------
Need help in getting to the root of this and fixing it. [~lamberken] [~leesf] : Currently, I am planning to increase Xmx setting to 4G to workaround. But, need your help in getting to the bottom of this. Would you be interested in taking this ?
Balaji.V
> Debug possible memory leaks when running tests in hudi-client
> -------------------------------------------------------------
>
> Key: HUDI-997
> URL: https://issues.apache.org/jira/browse/HUDI-997
> Project: Apache Hudi
> Issue Type: Task
> Components: Testing
> Reporter: Balaji Varadarajan
> Priority: Major
>
> Using visualvm, noticed the memory leak pattern of gradual increase in reachable memory (after GC) as the tests progress.
> Some possible candidates where I noticed marked increase in memory while the tests were running :
>
> [INFO] Running org.apache.hudi.table.TestCleaner
> [INFO] Running org.apache.hudi.table.TestHoodieMergeOnReadTable
> [INFO] Running org.apache.hudi.table.action.commit.TestCopyOnWriteActionExecutor
> [INFO] Running org.apache.hudi.table.action.compact.TestAsyncCompaction
> [INFO] Running org.apache.hudi.index.hbase.TestHBaseIndex
> [INFO] Running org.apache.hudi.index.TestHoodieIndex
> [INFO] Running org.apache.hudi.client.TestHoodieClientOnCopyOnWriteStorage
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)