About mikopp

mikopp · ‎08-19-2013

Thanks Harsh, That was the tip I needed. I had already changed the map and reduce memory (and pretty much everything else) but I didn't know about the yarn.app.mapreduce.am.resource.mb and for some reason that was messed up. The ec2 setup of CFM put the 512 in my data nodes and 1.5 G in my node that ran all the master services. So the other way around. After giving the worker nodes 2.5 G and reducing the master to 512 it started running. I used the CFM to set things up, so this might be a bug there. Thanks again! Best Mike

mikopp · ‎08-14-2013

Hi, I used Cloudera Manager to setup a Cloudera Cluster in EC2 and have it setup to run Yarn instead of MRv1. However whenever I submit any jobs, the job gets accepted and is listed in the Resource Manager Web UI as accepted with final status undefined and tracking undefined. The job never starts I can find no errors whatsoever in any logs. Does anybody have an Idea why this could be? I suspect that the resource manager decides that there aren't the necessary resources available to run the job, jowever I have the tasks configured to run with 512 MB and that is definitely available... Thanks! Mike

Online	Offline
Last Visited	‎08-22-2013 03:42 AM

Member Since	‎08-14-2013 04:25 AM
Last Visited	‎08-22-2013 03:42 AM
Posts	2

Cloudera Community

Re: Yarn and submitting MapReduce jobs

Yarn and submitting MapReduce jobs