Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

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

Solved Go to solution
Highlighted

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

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

Accepted Solutions
Highlighted

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

Rising Star

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
Highlighted

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

Expert Contributor

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

Highlighted

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

Rising Star

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

Highlighted

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

Expert Contributor

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

Don't have an account?
Coming from Hortonworks? Activate your account here