Hi Chris,

Turns out it was my code's problem. For some reason the com.mysql.jdbc.Driver 
class wouldn't load, was throwing an exception and making the 
SystemFactory.getConsumer() return null, hence the container failing and the AM 
complaining.

I didn't realise this as there was only a small window of time in which I could 
access the container logs before it failed and the YARN UI shut me out of 
there. It didn't help that it's running on a remote node and would take a bit 
to load sometimes.

Finally managed to access the logs properly earlier, and it all then became 
apparent.

Thanks anyway, and will be sure to contribute back after I get things working.

Jonathan


------------------------------------------------------
From: Chris Riccomini [email protected]
Reply: [email protected] [email protected]
Date: 7 February 2014 at 10:10:12
To: [email protected] [email protected]
Subject:  Re: org.apache.hadoop.util.Shell$ExitCodeException whenever Samza 
container launches

>  
> Hey Jonathan,
>  
> Your container is definitely failing, but that's all the AM logs  
> can
> really say. Can you post and share the logs for your containers  
> (as
> opposed to the AM logs)? This will probably show the exception  
> that's
> triggering the exit code with a -1.
>  
> Also, the JDBC Database reader is something we've really wanted  
> for a
> while. It would be awesome if you could open a JIRA and post your  
> code
> when you're done, like you did with the file reader.
>  
> Thanks a bunch for your patience. Your contributions are pretty  
> exciting.
> These kinds of consumers are really important for Samza's ecosystem.  
>  
> Cheers,
> Chris
>  
> On 2/7/14 12:25 AM, "Jonathan Poltak Samosir"  
> wrote:
>  
> >Hi all,
> >
> >Currently experiencing a strange problem with a new Samza system  
> I am
> >writing to connect and read from databases via JDBC. I have based  
> it off
> >another system I have written to read from files (which works),  
> and at
> >the moment there are not a lot of differences apart from opening  
> a
> >database Connection rather than opening a Reader on a file.  
> >
> >The issue does not seem to be related to my code, going by the logs  
> and
> >how my code is directly based off another working system, although  
> I
> >could be wrong.
> >
> >If anyone has encountered a similar problem, or knows the reason  
> behind
> >this, I would love to hear your thoughts. Searching around,  
> I am yet to
> >find any solutions or explanations that fit with the problem  
> which I am
> >encountering.
> >
> >Here is the AM log:
> >https://gist.github.com/poltak/8858874
> >
> >If needed, my SystemFactory and SystemConsumer implementations  
> can be
> >found here:
> >https://github.com/poltak/hello-samza/tree/database-reader/samza-wikipedia  
> >/src/main/java/samza/examples/databasereader/system  
> >
> >Along with the config file I am using when the error occurs:
> >https://github.com/poltak/hello-samza/blob/database-reader/samza-job-packa  
> >ge/src/main/config/database-reader-feed.properties  
> >
> >Let me know if any further information is needed, and will update  
> this if
> >I find any solution/explanation.
> >
> >Thanks for your time,
> >Jonathan
> >
>  
>  

Reply via email to