Ok so I figured it out. It wasn't Scala exactly. The yarn container memory configuration was at the default, just on the threshold between java jar and a scala-based jar (containing the scala libs in addition to everything) so the scala jobs were just big enough to cause the yarn containers to not have enough ram.
Thanks! On Wed, Feb 22, 2017 at 10:59 PM, Tushar Gosavi <[email protected]> wrote: > Hi Chris, > > Can you provide logs to the container where Scala operators are running? > what version of scala and apex are you using? If possible can you provide > scala operator code for me to test. > > Thanks. > - Tushar. > > > > On Wed, Feb 22, 2017 at 5:15 AM, Chris Benninger <[email protected]> > wrote: > >> I will also mention that I followed these instructions: https://www.data >> torrent.com/blog/blog-writing-apache-apex-application-in-scala/ >> >> On Tue, Feb 21, 2017 at 3:44 PM, Chris Benninger <[email protected]> >> wrote: >> >>> I cannot get any scala operators to actually work. The Job starts and >>> says running but any Scala Operators do not kick off. It shows them in >>> Pending_Deploy state. I see nothing unusual in the logs. >>> >>> >>> >> >
