Hey Arbi, If you're missing the samza-api JAR, you're probably missing the rest as well, which would cause the job to fail. I recommend taking a look at what's in your job's .tgz file. In the lib directory, there should be a bunch of JARs, including samza-api, samza-core, etc. If there's not, you have a problem with your package assembly. This can be fixed by updating the assembly/src.xml file accordingly.
Cheers, Chris On 11/19/14 2:53 PM, "Arbi Akhina" <[email protected]> wrote: >Hi, >I'm having trouble getting to work a modified version of the of >hello-samza >(i just replaced the 3 wikipedia streaming tasks with my own task). > >When I do *mvn clean package* and then extract the generated tar.gz file I >can't find samza-api.jar & sl4j-api.jar under the lib folder which cause >the failure of the submission (i.e. run-job.sh) with a class not found >exception. > >I had to add these jars manually so that the submission works but then on >the ResourceManger's UI I see the job as failed (containers exiting with >something like -1000). I can't find the logs left by the app master or any >one of the containers. I'm enabling logs aggregation, on hdfs I can see a >log file with a name like appId_hostname_port.log but *yarn logs >-applicarionId <appId>* prints just the content of the classpath. > >Any hint that could help investigating this issue? > >bests
