Archives of Support Questions (Read Only)

Nilesh · ‎04-13-2016

Hi Team,

Job hang while importing tables via sqoop shown following message in web UI.

ACCEPTED: waiting for AM container to be allocated, launched and register with RM

Kindly suggest.

KuldeepK · ‎04-13-2016

@Nilesh

There are 2 unhealthy nodes, if you click on "2" under unhealthy nodes section, you will get reason why they are unhealthy, it could be because of bad disk etc. Please check and try to check nodemanager's logs, you will get more info in there.

View solution in original post

cherukuri_49 · ‎01-11-2017

Hi @Nilesh,

I am too facing same issue, could you please suggest me if you have solution.

smkmuthu · ‎08-03-2018

Hi All

I am also facing the same issue. but My server hard disk is new. There is no warning/alert in my Ambari level.

Once my current job completes, then only the second job is allowed to execute..

If my first job is running for 60 minutes, my second job is on hold. Any suggestions.

server capacity : 16 core , 64 GB RAM

Thx

Muthu

volker_kuechenh · ‎09-04-2018

Hi, this Looks like fifo-scheduling / capacity scheduling with 1 group only Try to switch to fair scheduling in yarn.

Regards,

Volker

Cloudera Community

Archives of Support Questions (Read Only)

Mapreduce job hang, waiting for AM container to be allocated.