I had a similar issue and many others - all were basically symptoms for yarn killing the container for high memory usage. Haven't gotten to root cause yet.
On Tue, Sep 9, 2014 at 3:18 PM, Marcelo Vanzin <van...@cloudera.com> wrote: > Your executor is exiting or crashing unexpectedly: > > On Tue, Sep 9, 2014 at 3:13 PM, Penny Espinoza > <pesp...@societyconsulting.com> wrote: > > org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor: Exit > > code from container container_1410224367331_0006_01_000003 is : 1 > > 2014-09-09 21:47:26,345 WARN > > org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor: > > Exception from container-launch with container ID: > > container_1410224367331_0006_01_000003 and exit code: 1 > > You can check the app logs (yarn logs --applicationId [id]) and see > why the container is exiting. There's probably an exception happening > somewhere. > > > -- > Marcelo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@spark.apache.org > For additional commands, e-mail: user-h...@spark.apache.org > >
