Anurag Mantripragada created IMPALA-9119: --------------------------------------------
Summary: query_test.test_tpch_queries.TestTpchQuery.test_tpch failed with "Memory limit Exceeded." Key: IMPALA-9119 URL: https://issues.apache.org/jira/browse/IMPALA-9119 Project: IMPALA Issue Type: Bug Components: Backend Affects Versions: Impala 3.3.0 Reporter: Anurag Mantripragada Observed during a GVD run here: [https://jenkins.impala.io/job/ubuntu-16.04-dockerised-tests/1529/] Part of the error message: {code:java} E ImpalaBeeswaxException: ImpalaBeeswaxException: E Query aborted:Memory limit exceeded: Cannot perform aggregation at aggregator with id 4. Failed to allocate 25 bytes for intermediate tuple. E Fragment 85444bc502604143:43739df80000000b could not allocate 25.00 B without exceeding limit. E Error occurred on backend e6a3e789bfca:22000 by fragment 85444bc502604143:43739df80000000b E Memory left in process limit: 6.82 GB E Memory left in query limit: 10.48 KB {code} Aggregation node id 4: {code:java} E Fragment 85444bc502604143:43739df80000000b: Reservation=42.00 MB OtherMemory=1.64 MB Total=43.64 MB Peak=43.70 MB E AGGREGATION_NODE (id=4): Reservation=42.00 MB OtherMemory=42.12 KB Total=42.04 MB Peak=42.04 MB E GroupingAggregator 0: Reservation=42.00 MB OtherMemory=17.12 KB Total=42.02 MB Peak=42.02 MB E Exprs: Total=17.12 KB Peak=17.12 KB E KUDU_SCAN_NODE (id=3): Total=1.49 MB Peak=1.51 MB E Queued Batches: Total=1.49 MB Peak=1.51 MB E KrpcDataStreamSender (dst_id=13): Total=83.35 KB Peak=99.35 KB E CodeGen: Total=5.29 KB Peak=596.50 KB {code} -- This message was sent by Atlassian Jira (v8.3.4#803005)