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.

Sqoop Job is not moving from Accepted to Running state

Sqoop Job is not moving from Accepted to Running state

80448-rmissue.png

My job is not moving from Accepted state to Running state.Can you suggest me??

[Tue Jul 10 07:04:49 -0700 2018] 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:19456, vCores:1>; Queue Resource Limit for AM = <memory:16384, vCores:1>; User AM Resource Limit of the queue = <memory:16384, vCores:1>; Queue AM Resource Usage = <memory:1024, vCores:1>;

rmissue.png

Currently Only one job is running.

1 REPLY 1

Re: Sqoop Job is not moving from Accepted to Running state

Hello @Divakar Annapureddy!
Could you provide the following parameters?

yarn.scheduler.capacity.maximum-applications
yarn.scheduler.capacity.<queue-path>.maximum-applications
yarn.scheduler.capacity.<queue-path>.maximum-capacity yarn.scheduler.capacity.maximum-am-resource-percent
yarn.scheduler.capacity.<queue-path>.maximum-am-resource-percent
yarn.scheduler.minimum-allocation-mb
yarn.app.mapreduce.am.resource.mb
yarn.scheduler.maximum-allocation-mb
yarn.scheduler.minimum-allocation-mb

Also, if you're setting your queue, take a look at this link
https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.6.5/bk_yarn-resource-management/content/setting...

Thanks!

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