Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Beeline query not getting launched - Queue's AM resource limit exceeded

avatar
Expert Contributor
application-attempt-appattempt-1493666070215-0013.pdf

Hi - i'm running a Beeline query, and it is not getting launched.

Query :

beeline -u jdbc:hive2://nwk2-bdp-hadoop-07.gdcs-qa.apple.com:10000/default -n hive -e "INSERT INTO factsales SELECT * FROM factsales_tmp"

Error on the Resource Manager UI is as shown ->

--------------------------------

[Mon May 01 21:31:00 +0000 2017] Application is added to the scheduler and is not yet activated. Queue's AM resource limit exceeded. Details : AM Partition = <DEFAULT_PARTITION>; AM Resource Request = <memory:2048, vCores:1>; Queue Resource Limit for AM = <memory:2048, vCores:1>; User AM Resource Limit of the queue = <memory:2048, vCores:1>; Queue AM Resource Usage = <memory:2048, vCores:1>;

--------------------------------

The Execution engine is - MapReduce

Also, This is using default queue. I've another queue - llap which is used to run Hiveserver2 Intearctive (% of Cluster Capacity = 40%)

Any ideas on what needs to be done/tweaked for this ?

1 ACCEPTED SOLUTION

avatar
Expert Contributor

What is the value of yarn.scheduler.capacity.maximum-am-resource-percent in your cluster? The default value is usually 0.2. Try increasing it and see if your job moves forward.

View solution in original post

3 REPLIES 3

avatar
Expert Contributor

@Neeraj Sabharwal, @mqureshi, @Artem Ervits -looping you in, any ideas on this ?

avatar
Expert Contributor

What is the value of yarn.scheduler.capacity.maximum-am-resource-percent in your cluster? The default value is usually 0.2. Try increasing it and see if your job moves forward.

avatar
Expert Contributor

@Gour Saha - thanks, that setting fixed the issue !