[
https://issues.apache.org/jira/browse/HIVE-27695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767548#comment-17767548
]
Stamatis Zampetakis commented on HIVE-27695:
--------------------------------------------
To obtain the heapdump from the TestMiniTezCliDriver I modified the following
properties in "data/conf/tez/hive-site.xml" file as follows:
{code:xml}
<property>
<name>hive.tez.java.opts</name>
<value> -Dlog4j.configurationFile=tez-container-log4j2.properties
-Dtez.container.log.level=INFO -Dtez.container.root.logger=CLA
-XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=/home/stamatis/Issues/tez_union_oom/child</value>
</property>
<property>
<name>tez.am.launch.cmd-opts</name>
<value> -Dlog4j.configurationFile=tez-container-log4j2.properties
-Dtez.container.log.level=INFO -Dtez.container.root.logger=CLA
-XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=/home/stamatis/Issues/tez_union_oom/am</value>
</property>
{code}
> Intermittent OOM when running TestMiniTezCliDriver
> --------------------------------------------------
>
> Key: HIVE-27695
> URL: https://issues.apache.org/jira/browse/HIVE-27695
> Project: Hive
> Issue Type: Bug
> Components: Test
> Affects Versions: 4.0.0-beta-1
> Reporter: Stamatis Zampetakis
> Assignee: Stamatis Zampetakis
> Priority: Major
> Attachments: am_heap_dumps.tar.xz, leak_suspect_1.png
>
>
> Running all the tests under TestMiniTezCliDriver very frequently (but still
> intermittently) leads to OutOfMemory errors.
> {noformat}
> cd itests/qtest && mvn test -Dtest=TestMiniTezCliDriver
> {noformat}
> I set {{-XX:+HeapDumpOnOutOfMemoryError}} and the respective heapdumps are
> attached to this ticket.
> The OOM is thrown from the application master and a quick inspection of the
> dumps shows that it comes mainly from the accumulation of Configuration
> objects (~1MB each) by various classes.
> The max heap size for application master is pretty low (~100MB) so it is
> quite easy to reach. The heap size is explicitly very low for testing
> purposes but maybe we should re-evaluate the current configurations for the
> tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
