[
https://issues.apache.org/jira/browse/IMPALA-12429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17775859#comment-17775859
]
Riza Suminto commented on IMPALA-12429:
---------------------------------------
This seems like an admission control setting issue for the test minicluster.
Yes, failing query do seem like a large query type, where running it with high
degree of parallelism might overwhelm available memory in minicluster. I think
it best to disable specific large queries from this test.
> TestTpcdsQueryWithProcessingCost.test_tpcds_q51a and
> TestTpcdsQuery.test_tpcds_q67a failed
> ------------------------------------------------------------------------------------------
>
> Key: IMPALA-12429
> URL: https://issues.apache.org/jira/browse/IMPALA-12429
> Project: IMPALA
> Issue Type: Bug
> Components: Frontend
> Reporter: Wenzhe Zhou
> Assignee: Riza Suminto
> Priority: Critical
>
> The test failed after the patch for IMPALA-12408 (Optimize
> HdfsScanNode.computeScanRangeLocations) was merged. It may be related.
> Stacktrace
> {code:java}
> query_test/test_tpcds_queries.py:196: in test_tpcds_q51a
> self.run_test_case(self.get_workload() + '-q51a', vector)
> common/impala_test_suite.py:718: in run_test_case
> result = exec_fn(query, user=test_section.get('USER', '').strip() or None)
> common/impala_test_suite.py:656: in __exec_in_impala
> result = self.__execute_query(target_impalad_client, query, user=user)
> common/impala_test_suite.py:992: in __execute_query
> return impalad_client.execute(query, user=user)
> common/impala_connection.py:214: in execute
> return self.__beeswax_client.execute(sql_stmt, user=user)
> beeswax/impala_beeswax.py:191: in execute
> handle = self.__execute_query(query_string.strip(), user=user)
> beeswax/impala_beeswax.py:369: in __execute_query
> self.wait_for_finished(handle)
> beeswax/impala_beeswax.py:390: in wait_for_finished
> raise ImpalaBeeswaxException("Query aborted:" + error_log, None)
> E ImpalaBeeswaxException: ImpalaBeeswaxException:
> E Query aborted:Failed to get minimum memory reservation of 2.82 GB on
> daemon impala-ec2-centos79-m6i-4xlarge-ondemand-0c5c.vpc.cloudera.com:27000
> for query 95482fe28499fbef:6bed6d8400000000 due to following error: Memory
> limit exceeded: Could not allocate memory while trying to increase
> reservation.
> E Query(95482fe28499fbef:6bed6d8400000000) could not allocate 2.82 GB
> without exceeding limit.
> E Error occurred on backend
> impala-ec2-centos79-m6i-4xlarge-ondemand-0c5c.vpc.cloudera.com:27000
> E Memory left in process limit: 3.63 GB
> E Query(95482fe28499fbef:6bed6d8400000000): Reservation=0
> ReservationLimit=9.60 GB OtherMemory=0 Total=0 Peak=0
> E Memory is likely oversubscribed. Reducing query concurrency or
> configuring admission control may help avoid this error.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
