You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@samza.apache.org by Jordi Blasi Uribarri <jb...@nextel.es> on 2015/09/29 11:42:18 UTC
Versioning question
I was going through files I have in the system and I found some strange things that make me wonder about correct versioning. I am not sure but It may be the origin of the problems I see.
When I installed Samza I ran the following:
git clone http://git-wip-us.apache.org/repos/asf/samza.git
cd samza
./gradlew clean build
I thought that this was getting the last stable version (0.9.1) but I have found that the compiled jars in my installation are named like this:
samza-kv-rocksdb_2.10-0.10.0-SNAPSHOT.jar
samza-core_2.10-0.10.0-SNAPSHOT.jar
samza-api-0.10.0-SNAPSHOT.jar
So as I understand it, I have samza 0.10.0 version installed and for scala 2.10. Is this correct?
Kafka is installed with 2.9 scala. I am not sure if this is the conflicting element. Should I go to 2.10?
Hadoop and yarn are version 2.6.0. Should I go to 2.7.1?
I have tried to place in the lib folder the jar files generated in the samza compilation (2.10-0.10.0) and they show completely different messages. Now I see an error that ask for a new library that I cannot locate.
Exception in thread "main" java.lang.NoClassDefFoundError: joptsimple/OptionSpec
at org.apache.samza.job.JobRunner$.main(JobRunner.scala:39)
at org.apache.samza.job.JobRunner.main(JobRunner.scala)
Caused by: java.lang.ClassNotFoundException: joptsimple.OptionSpec
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
Do I have a versioning issue? Which library does this class belong to?
Thanks
Jordi
________________________________
Jordi Blasi Uribarri
Área I+D+i
jblasi@nextel.es
Oficina Bilbao
[http://www.nextel.es/wp-content/uploads/Firma_Nextel_2015.png]
Re: Versioning question
Posted by Yi Pan <ni...@gmail.com>.
Wohoo! That's great! Hope to hear more good news from you!
-Yi
On Wed, Sep 30, 2015 at 7:39 AM, Jordi Blasi Uribarri <jb...@nextel.es>
wrote:
> I finally got it working. I have had a communication problem with Kafka
> and looks like the topics were corrupt, so the Job launching process was
> not being able to get them running. Kafka reinstallation, new topics and
> now I have 3 jobs running.
>
> Thanks.
>
> Jordi
>
> -----Mensaje original-----
> De: Yi Pan [mailto:nickpan47@gmail.com]
> Enviado el: miércoles, 30 de septiembre de 2015 15:29
> Para: dev@samza.apache.org
> Asunto: Re: Versioning question
>
> Hi, Jordi,
>
> Yeah, first to clarify, master(trunk) is beyond the current release. You
> should be able to find a branch 0.9.1 that actually is the current released
> version.
>
> And the following combination is verified:
> 1) JDK7
> 2) Scala 2.10
> 3) Yarn 2.6
> 4) Kafka 0.8.2.1
>
> I would recommend to cleanup your installed copies and try to have the
> above sets of components installed before you proceed.
>
> Thanks!
>
> -Yi
>
> On Tue, Sep 29, 2015 at 2:42 AM, Jordi Blasi Uribarri <jb...@nextel.es>
> wrote:
>
> > I was going through files I have in the system and I found some
> > strange things that make me wonder about correct versioning. I am not
> > sure but It may be the origin of the problems I see.
> >
> > When I installed Samza I ran the following:
> > git clone http://git-wip-us.apache.org/repos/asf/samza.git
> > cd samza
> > ./gradlew clean build
> >
> > I thought that this was getting the last stable version (0.9.1) but I
> > have found that the compiled jars in my installation are named like this:
> > samza-kv-rocksdb_2.10-0.10.0-SNAPSHOT.jar
> > samza-core_2.10-0.10.0-SNAPSHOT.jar
> > samza-api-0.10.0-SNAPSHOT.jar
> >
> > So as I understand it, I have samza 0.10.0 version installed and for
> > scala 2.10. Is this correct?
> >
> > Kafka is installed with 2.9 scala. I am not sure if this is the
> > conflicting element. Should I go to 2.10?
> >
> > Hadoop and yarn are version 2.6.0. Should I go to 2.7.1?
> >
> > I have tried to place in the lib folder the jar files generated in the
> > samza compilation (2.10-0.10.0) and they show completely different
> > messages. Now I see an error that ask for a new library that I cannot
> > locate.
> >
> > Exception in thread "main" java.lang.NoClassDefFoundError:
> > joptsimple/OptionSpec
> > at org.apache.samza.job.JobRunner$.main(JobRunner.scala:39)
> > at org.apache.samza.job.JobRunner.main(JobRunner.scala)
> > Caused by: java.lang.ClassNotFoundException: joptsimple.OptionSpec
> > at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> > at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> > at java.security.AccessController.doPrivileged(Native Method)
> > at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> > at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> > at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> >
> > Do I have a versioning issue? Which library does this class belong to?
> >
> > Thanks
> >
> > Jordi
> > ________________________________
> > Jordi Blasi Uribarri
> > Área I+D+i
> >
> > jblasi@nextel.es
> > Oficina Bilbao
> >
> > [http://www.nextel.es/wp-content/uploads/Firma_Nextel_2015.png]
> >
>
RE: Versioning question
Posted by Jordi Blasi Uribarri <jb...@nextel.es>.
I finally got it working. I have had a communication problem with Kafka and looks like the topics were corrupt, so the Job launching process was not being able to get them running. Kafka reinstallation, new topics and now I have 3 jobs running.
Thanks.
Jordi
-----Mensaje original-----
De: Yi Pan [mailto:nickpan47@gmail.com]
Enviado el: miércoles, 30 de septiembre de 2015 15:29
Para: dev@samza.apache.org
Asunto: Re: Versioning question
Hi, Jordi,
Yeah, first to clarify, master(trunk) is beyond the current release. You should be able to find a branch 0.9.1 that actually is the current released version.
And the following combination is verified:
1) JDK7
2) Scala 2.10
3) Yarn 2.6
4) Kafka 0.8.2.1
I would recommend to cleanup your installed copies and try to have the above sets of components installed before you proceed.
Thanks!
-Yi
On Tue, Sep 29, 2015 at 2:42 AM, Jordi Blasi Uribarri <jb...@nextel.es>
wrote:
> I was going through files I have in the system and I found some
> strange things that make me wonder about correct versioning. I am not
> sure but It may be the origin of the problems I see.
>
> When I installed Samza I ran the following:
> git clone http://git-wip-us.apache.org/repos/asf/samza.git
> cd samza
> ./gradlew clean build
>
> I thought that this was getting the last stable version (0.9.1) but I
> have found that the compiled jars in my installation are named like this:
> samza-kv-rocksdb_2.10-0.10.0-SNAPSHOT.jar
> samza-core_2.10-0.10.0-SNAPSHOT.jar
> samza-api-0.10.0-SNAPSHOT.jar
>
> So as I understand it, I have samza 0.10.0 version installed and for
> scala 2.10. Is this correct?
>
> Kafka is installed with 2.9 scala. I am not sure if this is the
> conflicting element. Should I go to 2.10?
>
> Hadoop and yarn are version 2.6.0. Should I go to 2.7.1?
>
> I have tried to place in the lib folder the jar files generated in the
> samza compilation (2.10-0.10.0) and they show completely different
> messages. Now I see an error that ask for a new library that I cannot
> locate.
>
> Exception in thread "main" java.lang.NoClassDefFoundError:
> joptsimple/OptionSpec
> at org.apache.samza.job.JobRunner$.main(JobRunner.scala:39)
> at org.apache.samza.job.JobRunner.main(JobRunner.scala)
> Caused by: java.lang.ClassNotFoundException: joptsimple.OptionSpec
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>
> Do I have a versioning issue? Which library does this class belong to?
>
> Thanks
>
> Jordi
> ________________________________
> Jordi Blasi Uribarri
> Área I+D+i
>
> jblasi@nextel.es
> Oficina Bilbao
>
> [http://www.nextel.es/wp-content/uploads/Firma_Nextel_2015.png]
>
Re: Versioning question
Posted by Yi Pan <ni...@gmail.com>.
Hi, Jordi,
Yeah, first to clarify, master(trunk) is beyond the current release. You
should be able to find a branch 0.9.1 that actually is the current released
version.
And the following combination is verified:
1) JDK7
2) Scala 2.10
3) Yarn 2.6
4) Kafka 0.8.2.1
I would recommend to cleanup your installed copies and try to have the
above sets of components installed before you proceed.
Thanks!
-Yi
On Tue, Sep 29, 2015 at 2:42 AM, Jordi Blasi Uribarri <jb...@nextel.es>
wrote:
> I was going through files I have in the system and I found some strange
> things that make me wonder about correct versioning. I am not sure but It
> may be the origin of the problems I see.
>
> When I installed Samza I ran the following:
> git clone http://git-wip-us.apache.org/repos/asf/samza.git
> cd samza
> ./gradlew clean build
>
> I thought that this was getting the last stable version (0.9.1) but I have
> found that the compiled jars in my installation are named like this:
> samza-kv-rocksdb_2.10-0.10.0-SNAPSHOT.jar
> samza-core_2.10-0.10.0-SNAPSHOT.jar
> samza-api-0.10.0-SNAPSHOT.jar
>
> So as I understand it, I have samza 0.10.0 version installed and for scala
> 2.10. Is this correct?
>
> Kafka is installed with 2.9 scala. I am not sure if this is the
> conflicting element. Should I go to 2.10?
>
> Hadoop and yarn are version 2.6.0. Should I go to 2.7.1?
>
> I have tried to place in the lib folder the jar files generated in the
> samza compilation (2.10-0.10.0) and they show completely different
> messages. Now I see an error that ask for a new library that I cannot
> locate.
>
> Exception in thread "main" java.lang.NoClassDefFoundError:
> joptsimple/OptionSpec
> at org.apache.samza.job.JobRunner$.main(JobRunner.scala:39)
> at org.apache.samza.job.JobRunner.main(JobRunner.scala)
> Caused by: java.lang.ClassNotFoundException: joptsimple.OptionSpec
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>
> Do I have a versioning issue? Which library does this class belong to?
>
> Thanks
>
> Jordi
> ________________________________
> Jordi Blasi Uribarri
> Área I+D+i
>
> jblasi@nextel.es
> Oficina Bilbao
>
> [http://www.nextel.es/wp-content/uploads/Firma_Nextel_2015.png]
>