Managed to resolve the issue. Gist of what I have been trying to do and the resolution -
I built a custom medium/long running yarn application with spring-hadoop and spring-boot and was trying to orchestrate it as an oozie java/shell action. Triggering it as a java action had a bunch of spring-hadoop/boot dependency conflict issues in run time. So I focused on triggering it as a shell action instead. Although it looked promising, there was a little config issue - my spring yarn application had the yarn client, container and app master packaged as a single executable. When executed via shell, it was supposed to start the yarn client - but instead it was always starting in yarn container mode as oozie shell was imitating the yarn client. Had to unset 'HADOOP_TOKEN_FILE_LOCATION' for the spring-yarn application to start in client mode. Thanks, Som On Tue, May 12, 2015 at 10:42 PM, Harsh J <[email protected]> wrote: > > Problem is both JavaAction and ShellAction launchers invoke the custom > yarn app as > 'MAPREDUCE' instead of 'YARN'. > > Could you elaborate on this? What log indicates this happening and > what error do you specifically observe? > > On Tue, May 12, 2015 at 7:08 AM, Som Satpathy <[email protected]> > wrote: > > Hi all, > > > > I am trying to run a custom yarn application container of type 'YARN' as > > part of an oozie workflow. Although I have been able to successfully run > > the yarn application via 'hadoop jar <jar> ...', I have not been able to > > run it either as a JavaAction or as a ShellAction. Problem is both > > JavaAction and ShellAction launchers invoke the custom yarn app as > > 'MAPREDUCE' instead of 'YARN'. > > > > Has any one tried something similar? Appreciate any pointers. > > > > Thanks, > > Som > > > > -- > Harsh J >
