Re: new to hadoop, jobs never leaving accepted

2019-07-10 Thread Sunil Govindan
Hi Jason Default value of yarn.scheduler.capacity..maximum-am-resource-percent is 0.1 (which is 10% of resource of the queue). If you want to run more apps in that queue, you need to increase this limit to run Application Master's for the apps. Please make sure this is not configured to a higher

Re: new to hadoop, jobs never leaving accepted

2019-07-10 Thread Jason Laughman
I added a couple of bigger servers and now I see multiple containers running, but I still can’t get a job to run. The job details now say: Diagnostics:[Wed Jul 10 17:27:59 + 2019] Application is added to the scheduler and is not yet activated. Queue's AM resource limit exceeded.

Re: new to hadoop, jobs never leaving accepted

2019-07-10 Thread yangtao.yt
Hi, Jason. According to the information you provided, your cluster has two nodes with the same resource , the single running container is AM container which already takes over . I think a possible cause is that available resource of your cluster was insufficient for requesting new containers,

new to hadoop, jobs never leaving accepted

2019-07-09 Thread Jason Laughman
I’ve been setting up a Hadoop 2.9.1 cluster and have data replicating through HDFS, but when I try to run a job via Hive (I see that it’s deprecated, but it’s what I’m working with for now) it never gets out of accepted state in the web tool. I’ve done some Googling and the general consensus