David Rorke created IMPALA-12167:
------------------------------------
Summary: TestJvmMemTracker.test_jvm_mem_tracking crashing impalad
during startup
Key: IMPALA-12167
URL: https://issues.apache.org/jira/browse/IMPALA-12167
Project: IMPALA
Issue Type: Bug
Components: be
Reporter: David Rorke
Assignee: Michael Smith
Attachments: ba01e6dd-9f36-44d6-9887dcb4-2df3f965.dmp_dumped.gz
test_jvm_mem_tracking is failing and causing the impalad to abort/crash early
during startup. Minidump is attached.
The test starts impala with the following arguments:
{noformat}
start-impala-cluster.py '--state_store_args=--statestore_update_frequency_ms=50
--statestore_priority_update_frequency_ms=50
--statestore_heartbeat_frequency_ms=50' --cluster_size=1 --num_coordinators=1
--log_dir=/data/jenkins/workspace/impala-asf-master-exhaustive/repos/Impala/logs/custom_cluster_tests
--log_level=1 '--impalad_args=--mem_limit_includes_jvm=true
--codegen_cache_capacity=0 ' '--state_store_args=None ' --jvm_args=-Xmx1g
--impalad_args=–default_query_options={noformat}
This test is unusual in setting --mem_limit_includes_jvm=true in the startup
flags, so it seems likely the failure is related to use of this flag. There
was also recent change to the Java startup options in IMPALA-11260 (to "add
add-opens to JAVA_TOOL_OPTIONS on startup") that could be related.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
