RE: AWS EMR: Container is running beyond virtual memory limits

I was under the understanding that with EMR 4.x, we had to create separate config files and place them on S3, then reference them when we create the cluster as described in detail in this first article: http://docs.aws.amazon.com/ElasticMapReduce/latest/ReleaseGuide/emr-release-differences.html

RE: AWS EMR: Container is running beyond virtual memory limits

I was under the understanding that with EMR 4.x, we had to create separate config files and place them on S3, then reference them when we create the cluster as described in detail in this first article: http://docs.aws.amazon.com/ElasticMapReduce/latest/ReleaseGuide/emr-release-differences.html

Re: AWS EMR: Container is running beyond virtual memory limits

Hi, It seems that the above mentioned configurations didn't take effect. Those changes were made in: /etc/Hadoop/conf/yarn-site.xml And malted-site.xml @Sandeep even pidemo didn't run. On Fri, 11 Mar 2016 8:34 pm Pradeep A. Dalvi, wrote: > We are facing following error

Re: AWS EMR: Container is running beyond virtual memory limits

What is the memory allocated to the container? On 11-Mar-2016 8:34 pm, "Pradeep A. Dalvi" wrote: > We are facing following error message while starting any containers on AWS > EMR. > > Container [pid=8107,containerID=container_1457702160744_0001_01_07] is > running beyond