Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Query exhausted resources at this scale factor

I was running SQL query on Amazon Athena. And I got the following error couple of times:

Query exhausted resources at this scale factor

This query ran against the "test1" database, unless qualified by the query. Please post the error message on our forum or contact customer support with Query Id: *************

like image 398
Ridwan Avatar asked Aug 03 '17 17:08

Ridwan


People also ask

What is Athena query?

Amazon Athena is an interactive query service that makes it easy to analyze data in Amazon S3 using standard SQL. Athena is serverless, so there is no infrastructure to manage, and you pay only for the queries that you run.

How much does Athena cost?

Amazon Athena Pricing Explained Athena costs $5 per TB of compressed data scanned. While you incur no additional costs for DDL statements or failed queries, standard charges of other AWS resources like S3 bucket, Lambda, Glue Data Catalog, etc., apply if provisioned.

What is workgroup in Athena?

You can now use Amazon Athena Workgroups - A new resource type that can be used to separate query execution and query history between Users, Teams, or Applications running under the same AWS account. Because Workgroups act as resources, you can use resource-based policies to control access to a Workgroup.


1 Answers

Without seeing the query it's hard to say for sure what the problem is, but it's very likely that it is due to an internal issue in Athena that has to do with sorting of large intermediary result sets.

The version of Presto that Athena uses does not have support for sorting datasets that are too big to fit in memory. It used to be the same for aggregations too, but that has been fixed by the Athena team.

The issue most often occurs when you have very wide tables, i.e. many columns, or columns with a lot of data. Each individual row can represent a big chunk of memory, and if a node runs out of memory while trying to sort its chunk the query aborts with the "query exhausted resources at this scale factor" error.

If this matches your situation the only way around is unfortunately to limit the number of columns, or eliminate the sorting. Sometimes you can rearrange the query to do the sorting at a different stage to make the memory pressure on the sorting stage lower.

like image 142
Theo Avatar answered Sep 21 '22 06:09

Theo