Hi Robin, In the Elastic MapReduce debugging interface logs show up after tasks complete. If you’d like to get to the Hadoop tracker interface, you can do it in the EMR job flow by using the steps described here: http://docs.amazonwebservices.com/ElasticMapReduce/latest/DeveloperGuide/index.html?AccessingtheHadoopUserInterfacetoMonitorJobStatus.html
Regards, Peter Sirota From: Robin Anil <robin.a...@gmail.com<mailto:robin.a...@gmail.com>> Date: February 27, 2010 13:44:13 PST To: "mahout-dev@lucene.apache.org<mailto:mahout-dev@lucene.apache.org>" <mahout-dev@lucene.apache.org<mailto:mahout-dev@lucene.apache.org>> Subject: Re: Who owns mahout bucket on s3? Reply-To: "mahout-dev@lucene.apache.org<mailto:mahout-dev@lucene.apache.org>" <mahout-dev@lucene.apache.org<mailto:mahout-dev@lucene.apache.org>> Aargh. The emr is executing but there is no feedback other than knowing 6 maps are executing 3 in running state and 3 in pending (for 5 mins now). No logs. This totally sucks. I am burning 6 c1 medium machines. I should be getting atleast 12 mappers running as c1s are 2 core. I would rather go back to clouderas cluster with the hadoop tracker interface Robin
