You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@samza.apache.org by Jack Huang <ja...@machinezone.com> on 2016/02/27 03:21:17 UTC
Error when fetching configuration from coordinator
Hi all,
Still trying to get hello-samza running on our cluster. After I
successfully launched the hello-samza job with
*deploy/samza/bin/run-job.sh
--config-factory=org.apache.samza.config.factories.PropertiesConfigFactory
--config-path=file://$PWD/deploy/samza/config/wikipedia-feed.properties*
, I get the following Exception in the log:
*LogType:samza-container-0.log*
*Log Upload Time:Sat Feb 27 01:29:13 +0000 2016*
*LogLength:993*
*Log Contents:*
*2016-02-27 01:28:30 SamzaContainer$ [INFO] Got container ID: 0*
*2016-02-27 01:28:30 SamzaContainer$ [INFO] Got coordinator URL:
http://node03:54179/ <http://node03:54179/>*
*2016-02-27 01:28:30 SamzaContainer$ [INFO] Fetching configuration from:
http://node03:54179/ <http://node03:54179/>*
*2016-02-27 01:28:30 SamzaContainerExceptionHandler [ERROR] Uncaught
exception in thread (name=main). Exiting process now.*
*java.io.EOFException: No content to map to Object due to end of input*
* at
org.codehaus.jackson.map.ObjectMapper._initForReading(ObjectMapper.java:2775)*
* at
org.codehaus.jackson.map.ObjectMapper._readMapAndClose(ObjectMapper.java:2718)*
* at
org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:1863)*
* at
org.apache.samza.container.SamzaContainer$.readJobModel(SamzaContainer.scala:109)*
* at
org.apache.samza.container.SamzaContainer$.safeMain(SamzaContainer.scala:83)*
* at
org.apache.samza.container.SamzaContainer$.main(SamzaContainer.scala:66)*
* at org.apache.samza.container.SamzaContainer.main(SamzaContainer.scala)*
*End of LogType:samza-container-0.log*
Can anyone help me figure out why it can't read the configuration file from
the coordinator URL?
Thanks,
Jack Huang
Re: Error when fetching configuration from coordinator
Posted by Jagadish Venkatraman <ja...@gmail.com>.
Are you able to connect to the port on the box? Try doing a wget first.
Do you have conflicting versions of Jackson on your classpath?
On Friday, February 26, 2016, Jack Huang <ja...@machinezone.com> wrote:
> Hi all,
>
> Still trying to get hello-samza running on our cluster. After I
> successfully launched the hello-samza job with
>
> *deploy/samza/bin/run-job.sh
> --config-factory=org.apache.samza.config.factories.PropertiesConfigFactory
> --config-path=file://$PWD/deploy/samza/config/wikipedia-feed.properties*
>
>
> , I get the following Exception in the log:
>
> *LogType:samza-container-0.log*
> *Log Upload Time:Sat Feb 27 01:29:13 +0000 2016*
> *LogLength:993*
> *Log Contents:*
> *2016-02-27 01:28:30 SamzaContainer$ [INFO] Got container ID: 0*
> *2016-02-27 01:28:30 SamzaContainer$ [INFO] Got coordinator URL:
> http://node03:54179/ <http://node03:54179/>*
> *2016-02-27 01:28:30 SamzaContainer$ [INFO] Fetching configuration from:
> http://node03:54179/ <http://node03:54179/>*
> *2016-02-27 01:28:30 SamzaContainerExceptionHandler [ERROR] Uncaught
> exception in thread (name=main). Exiting process now.*
> *java.io.EOFException: No content to map to Object due to end of input*
> * at
>
> org.codehaus.jackson.map.ObjectMapper._initForReading(ObjectMapper.java:2775)*
> * at
>
> org.codehaus.jackson.map.ObjectMapper._readMapAndClose(ObjectMapper.java:2718)*
> * at
> org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:1863)*
> * at
>
> org.apache.samza.container.SamzaContainer$.readJobModel(SamzaContainer.scala:109)*
> * at
>
> org.apache.samza.container.SamzaContainer$.safeMain(SamzaContainer.scala:83)*
> * at
> org.apache.samza.container.SamzaContainer$.main(SamzaContainer.scala:66)*
> * at org.apache.samza.container.SamzaContainer.main(SamzaContainer.scala)*
> *End of LogType:samza-container-0.log*
>
>
>
> Can anyone help me figure out why it can't read the configuration file from
> the coordinator URL?
>
> Thanks,
>
>
> Jack Huang
>
--
Sent from my iphone.
Re: Error when fetching configuration from coordinator
Posted by Jagadish Venkatraman <ja...@gmail.com>.
Perfect, Glad that this was resolved! :-)
On Mon, Feb 29, 2016 at 3:04 PM, Jack Huang <ja...@machinezone.com>
wrote:
> Jack Huang
>
> On Mon, Feb 29, 2016 at 12:52 PM, Jack Huang <ja...@machinezone.com>
> wrote:
>
> > Thanks a lot Jadadish! I changed jackson-jaxrs:1.8.5 to*
> > jackson-jaxrs:1.9.13* and added *jackson-mapper-asl:1.9.13*. Now
> > hello-samza finally runs :)
> >
> > <dependency>
> >
> > <groupId>org.codehaus.jackson</groupId>
> >
> > <artifactId>jackson-jaxrs</artifactId>
> >
> > <version>1.9.13</version>
> >
> > </dependency>
> >
> > <dependency>
> > <groupId>org.codehaus.jackson</groupId>
> > <artifactId>jackson-mapper-asl</artifactId>
> > <version>1.9.13</version>
> > </dependency>
> >
> > Not sure if adding jackson-core-asl or jackson-xc will change anything
> > though.
> >
> >
> > Jack Huang
> >
> > On Mon, Feb 29, 2016 at 11:50 AM, Jagadish Venkatraman <
> > jagadish1989@gmail.com> wrote:
> >
> >> I assume the issue was resolved after the version of Jackson was
> changed?
> >> Please refer https://issues.apache.org/jira/browse/YARN-2092 and
> >> SAMZA-878 for more context.
> >>
> >> Hadoop uses the following 4 jackson libs.
> >>
> >> <dependency>
> >> <groupId>org.codehaus.jackson</groupId>
> >> <artifactId>jackson-mapper-asl</artifactId>
> >> <version>1.9.13</version>
> >> </dependency>
> >> <dependency>
> >> <groupId>org.codehaus.jackson</groupId>
> >> <artifactId>jackson-core-asl</artifactId>
> >> <version>1.9.13</version>
> >> </dependency>
> >> <dependency>
> >> <groupId>org.codehaus.jackson</groupId>
> >> <artifactId>jackson-jaxrs</artifactId>
> >> <version>1.9.13</version>
> >> </dependency>
> >> <dependency>
> >> <groupId>org.codehaus.jackson</groupId>
> >> <artifactId>jackson-xc</artifactId>
> >> <version>1.9.13</version>
> >> </dependency>
> >>
> >>
> >> As long as you have all these to 1.9.13, you should be all set.
> >>
> >>
> >> Thanks,
> >> Jagadish
> >>
> >>
> >>
> >>
> >>
> >>
> >> On Mon, Feb 29, 2016 at 9:54 AM, Jack Huang <ja...@machinezone.com>
> >> wrote:
> >>
> >>> Hi Jagadish,
> >>>
> >>> I couldn't wget the coordinator URL. It appears that YARN/Samza retries
> >>> to run the job every time it fails, and each time the coordinator URL
> is
> >>> different.
> >>>
> >>> I did have to manually add a *jackson-mapper-asl:1.9.13* dependency to
> >>> pom.xml to resolve a* java.lang.ClassNotFoundException:
> >>> org.codehaus.jackson.map.deser.std.StdDeserializer* exception though...
> >>>
> >>> Thanks,
> >>>
> >>> Jack
> >>>
> >>> Jack Huang
> >>>
> >>> On Fri, Feb 26, 2016 at 6:21 PM, Jack Huang <jackhuang@machinezone.com
> >
> >>> wrote:
> >>>
> >>>> Hi all,
> >>>>
> >>>> Still trying to get hello-samza running on our cluster. After I
> >>>> successfully launched the hello-samza job with
> >>>>
> >>>> *deploy/samza/bin/run-job.sh
> >>>>
> --config-factory=org.apache.samza.config.factories.PropertiesConfigFactory
> >>>>
> --config-path=file://$PWD/deploy/samza/config/wikipedia-feed.properties*
> >>>>
> >>>>
> >>>> , I get the following Exception in the log:
> >>>>
> >>>> *LogType:samza-container-0.log*
> >>>> *Log Upload Time:Sat Feb 27 01:29:13 +0000 2016*
> >>>> *LogLength:993*
> >>>> *Log Contents:*
> >>>> *2016-02-27 01:28:30 SamzaContainer$ [INFO] Got container ID: 0*
> >>>> *2016-02-27 01:28:30 SamzaContainer$ [INFO] Got coordinator URL:
> >>>> http://node03:54179/ <http://node03:54179/>*
> >>>> *2016-02-27 01:28:30 SamzaContainer$ [INFO] Fetching configuration
> >>>> from: http://node03:54179/ <http://node03:54179/>*
> >>>> *2016-02-27 01:28:30 SamzaContainerExceptionHandler [ERROR] Uncaught
> >>>> exception in thread (name=main). Exiting process now.*
> >>>> *java.io.EOFException: No content to map to Object due to end of
> input*
> >>>> * at
> >>>>
> org.codehaus.jackson.map.ObjectMapper._initForReading(ObjectMapper.java:2775)*
> >>>> * at
> >>>>
> org.codehaus.jackson.map.ObjectMapper._readMapAndClose(ObjectMapper.java:2718)*
> >>>> * at
> >>>>
> org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:1863)*
> >>>> * at
> >>>>
> org.apache.samza.container.SamzaContainer$.readJobModel(SamzaContainer.scala:109)*
> >>>> * at
> >>>>
> org.apache.samza.container.SamzaContainer$.safeMain(SamzaContainer.scala:83)*
> >>>> * at
> >>>>
> org.apache.samza.container.SamzaContainer$.main(SamzaContainer.scala:66)*
> >>>> * at
> >>>> org.apache.samza.container.SamzaContainer.main(SamzaContainer.scala)*
> >>>> *End of LogType:samza-container-0.log*
> >>>>
> >>>>
> >>>>
> >>>> Can anyone help me figure out why it can't read the configuration file
> >>>> from the coordinator URL?
> >>>>
> >>>> Thanks,
> >>>>
> >>>>
> >>>> Jack Huang
> >>>>
> >>>
> >>>
> >>
> >>
> >> --
> >> Jagadish V,
> >> Graduate Student,
> >> Department of Computer Science,
> >> Stanford University
> >>
> >
> >
>
--
Jagadish V,
Graduate Student,
Department of Computer Science,
Stanford University
Re: Error when fetching configuration from coordinator
Posted by Jack Huang <ja...@machinezone.com>.
Jack Huang
On Mon, Feb 29, 2016 at 12:52 PM, Jack Huang <ja...@machinezone.com>
wrote:
> Thanks a lot Jadadish! I changed jackson-jaxrs:1.8.5 to*
> jackson-jaxrs:1.9.13* and added *jackson-mapper-asl:1.9.13*. Now
> hello-samza finally runs :)
>
> <dependency>
>
> <groupId>org.codehaus.jackson</groupId>
>
> <artifactId>jackson-jaxrs</artifactId>
>
> <version>1.9.13</version>
>
> </dependency>
>
> <dependency>
> <groupId>org.codehaus.jackson</groupId>
> <artifactId>jackson-mapper-asl</artifactId>
> <version>1.9.13</version>
> </dependency>
>
> Not sure if adding jackson-core-asl or jackson-xc will change anything
> though.
>
>
> Jack Huang
>
> On Mon, Feb 29, 2016 at 11:50 AM, Jagadish Venkatraman <
> jagadish1989@gmail.com> wrote:
>
>> I assume the issue was resolved after the version of Jackson was changed?
>> Please refer https://issues.apache.org/jira/browse/YARN-2092 and
>> SAMZA-878 for more context.
>>
>> Hadoop uses the following 4 jackson libs.
>>
>> <dependency>
>> <groupId>org.codehaus.jackson</groupId>
>> <artifactId>jackson-mapper-asl</artifactId>
>> <version>1.9.13</version>
>> </dependency>
>> <dependency>
>> <groupId>org.codehaus.jackson</groupId>
>> <artifactId>jackson-core-asl</artifactId>
>> <version>1.9.13</version>
>> </dependency>
>> <dependency>
>> <groupId>org.codehaus.jackson</groupId>
>> <artifactId>jackson-jaxrs</artifactId>
>> <version>1.9.13</version>
>> </dependency>
>> <dependency>
>> <groupId>org.codehaus.jackson</groupId>
>> <artifactId>jackson-xc</artifactId>
>> <version>1.9.13</version>
>> </dependency>
>>
>>
>> As long as you have all these to 1.9.13, you should be all set.
>>
>>
>> Thanks,
>> Jagadish
>>
>>
>>
>>
>>
>>
>> On Mon, Feb 29, 2016 at 9:54 AM, Jack Huang <ja...@machinezone.com>
>> wrote:
>>
>>> Hi Jagadish,
>>>
>>> I couldn't wget the coordinator URL. It appears that YARN/Samza retries
>>> to run the job every time it fails, and each time the coordinator URL is
>>> different.
>>>
>>> I did have to manually add a *jackson-mapper-asl:1.9.13* dependency to
>>> pom.xml to resolve a* java.lang.ClassNotFoundException:
>>> org.codehaus.jackson.map.deser.std.StdDeserializer* exception though...
>>>
>>> Thanks,
>>>
>>> Jack
>>>
>>> Jack Huang
>>>
>>> On Fri, Feb 26, 2016 at 6:21 PM, Jack Huang <ja...@machinezone.com>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> Still trying to get hello-samza running on our cluster. After I
>>>> successfully launched the hello-samza job with
>>>>
>>>> *deploy/samza/bin/run-job.sh
>>>> --config-factory=org.apache.samza.config.factories.PropertiesConfigFactory
>>>> --config-path=file://$PWD/deploy/samza/config/wikipedia-feed.properties*
>>>>
>>>>
>>>> , I get the following Exception in the log:
>>>>
>>>> *LogType:samza-container-0.log*
>>>> *Log Upload Time:Sat Feb 27 01:29:13 +0000 2016*
>>>> *LogLength:993*
>>>> *Log Contents:*
>>>> *2016-02-27 01:28:30 SamzaContainer$ [INFO] Got container ID: 0*
>>>> *2016-02-27 01:28:30 SamzaContainer$ [INFO] Got coordinator URL:
>>>> http://node03:54179/ <http://node03:54179/>*
>>>> *2016-02-27 01:28:30 SamzaContainer$ [INFO] Fetching configuration
>>>> from: http://node03:54179/ <http://node03:54179/>*
>>>> *2016-02-27 01:28:30 SamzaContainerExceptionHandler [ERROR] Uncaught
>>>> exception in thread (name=main). Exiting process now.*
>>>> *java.io.EOFException: No content to map to Object due to end of input*
>>>> * at
>>>> org.codehaus.jackson.map.ObjectMapper._initForReading(ObjectMapper.java:2775)*
>>>> * at
>>>> org.codehaus.jackson.map.ObjectMapper._readMapAndClose(ObjectMapper.java:2718)*
>>>> * at
>>>> org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:1863)*
>>>> * at
>>>> org.apache.samza.container.SamzaContainer$.readJobModel(SamzaContainer.scala:109)*
>>>> * at
>>>> org.apache.samza.container.SamzaContainer$.safeMain(SamzaContainer.scala:83)*
>>>> * at
>>>> org.apache.samza.container.SamzaContainer$.main(SamzaContainer.scala:66)*
>>>> * at
>>>> org.apache.samza.container.SamzaContainer.main(SamzaContainer.scala)*
>>>> *End of LogType:samza-container-0.log*
>>>>
>>>>
>>>>
>>>> Can anyone help me figure out why it can't read the configuration file
>>>> from the coordinator URL?
>>>>
>>>> Thanks,
>>>>
>>>>
>>>> Jack Huang
>>>>
>>>
>>>
>>
>>
>> --
>> Jagadish V,
>> Graduate Student,
>> Department of Computer Science,
>> Stanford University
>>
>
>
Re: Error when fetching configuration from coordinator
Posted by Jagadish Venkatraman <ja...@gmail.com>.
I assume the issue was resolved after the version of Jackson was changed?
Please refer https://issues.apache.org/jira/browse/YARN-2092 and SAMZA-878
for more context.
Hadoop uses the following 4 jackson libs.
<dependency>
<groupId>org.codehaus.jackson</groupId>
<artifactId>jackson-mapper-asl</artifactId>
<version>1.9.13</version>
</dependency>
<dependency>
<groupId>org.codehaus.jackson</groupId>
<artifactId>jackson-core-asl</artifactId>
<version>1.9.13</version>
</dependency>
<dependency>
<groupId>org.codehaus.jackson</groupId>
<artifactId>jackson-jaxrs</artifactId>
<version>1.9.13</version>
</dependency>
<dependency>
<groupId>org.codehaus.jackson</groupId>
<artifactId>jackson-xc</artifactId>
<version>1.9.13</version>
</dependency>
As long as you have all these to 1.9.13, you should be all set.
Thanks,
Jagadish
On Mon, Feb 29, 2016 at 9:54 AM, Jack Huang <ja...@machinezone.com>
wrote:
> Hi Jagadish,
>
> I couldn't wget the coordinator URL. It appears that YARN/Samza retries to
> run the job every time it fails, and each time the coordinator URL is
> different.
>
> I did have to manually add a *jackson-mapper-asl:1.9.13* dependency to
> pom.xml to resolve a* java.lang.ClassNotFoundException:
> org.codehaus.jackson.map.deser.std.StdDeserializer* exception though...
>
> Thanks,
>
> Jack
>
> Jack Huang
>
> On Fri, Feb 26, 2016 at 6:21 PM, Jack Huang <ja...@machinezone.com>
> wrote:
>
>> Hi all,
>>
>> Still trying to get hello-samza running on our cluster. After I
>> successfully launched the hello-samza job with
>>
>> *deploy/samza/bin/run-job.sh
>> --config-factory=org.apache.samza.config.factories.PropertiesConfigFactory
>> --config-path=file://$PWD/deploy/samza/config/wikipedia-feed.properties*
>>
>>
>> , I get the following Exception in the log:
>>
>> *LogType:samza-container-0.log*
>> *Log Upload Time:Sat Feb 27 01:29:13 +0000 2016*
>> *LogLength:993*
>> *Log Contents:*
>> *2016-02-27 01:28:30 SamzaContainer$ [INFO] Got container ID: 0*
>> *2016-02-27 01:28:30 SamzaContainer$ [INFO] Got coordinator URL:
>> http://node03:54179/ <http://node03:54179/>*
>> *2016-02-27 01:28:30 SamzaContainer$ [INFO] Fetching configuration from:
>> http://node03:54179/ <http://node03:54179/>*
>> *2016-02-27 01:28:30 SamzaContainerExceptionHandler [ERROR] Uncaught
>> exception in thread (name=main). Exiting process now.*
>> *java.io.EOFException: No content to map to Object due to end of input*
>> * at
>> org.codehaus.jackson.map.ObjectMapper._initForReading(ObjectMapper.java:2775)*
>> * at
>> org.codehaus.jackson.map.ObjectMapper._readMapAndClose(ObjectMapper.java:2718)*
>> * at
>> org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:1863)*
>> * at
>> org.apache.samza.container.SamzaContainer$.readJobModel(SamzaContainer.scala:109)*
>> * at
>> org.apache.samza.container.SamzaContainer$.safeMain(SamzaContainer.scala:83)*
>> * at
>> org.apache.samza.container.SamzaContainer$.main(SamzaContainer.scala:66)*
>> * at org.apache.samza.container.SamzaContainer.main(SamzaContainer.scala)*
>> *End of LogType:samza-container-0.log*
>>
>>
>>
>> Can anyone help me figure out why it can't read the configuration file
>> from the coordinator URL?
>>
>> Thanks,
>>
>>
>> Jack Huang
>>
>
>
--
Jagadish V,
Graduate Student,
Department of Computer Science,
Stanford University
Re: Error when fetching configuration from coordinator
Posted by Jack Huang <ja...@machinezone.com>.
Hi Jagadish,
I couldn't wget the coordinator URL. It appears that YARN/Samza retries to
run the job every time it fails, and each time the coordinator URL is
different.
I did have to manually add a *jackson-mapper-asl:1.9.13* dependency to
pom.xml to resolve a* java.lang.ClassNotFoundException:
org.codehaus.jackson.map.deser.std.StdDeserializer* exception though...
Thanks,
Jack
Jack Huang
On Fri, Feb 26, 2016 at 6:21 PM, Jack Huang <ja...@machinezone.com>
wrote:
> Hi all,
>
> Still trying to get hello-samza running on our cluster. After I
> successfully launched the hello-samza job with
>
> *deploy/samza/bin/run-job.sh
> --config-factory=org.apache.samza.config.factories.PropertiesConfigFactory
> --config-path=file://$PWD/deploy/samza/config/wikipedia-feed.properties*
>
>
> , I get the following Exception in the log:
>
> *LogType:samza-container-0.log*
> *Log Upload Time:Sat Feb 27 01:29:13 +0000 2016*
> *LogLength:993*
> *Log Contents:*
> *2016-02-27 01:28:30 SamzaContainer$ [INFO] Got container ID: 0*
> *2016-02-27 01:28:30 SamzaContainer$ [INFO] Got coordinator URL:
> http://node03:54179/ <http://node03:54179/>*
> *2016-02-27 01:28:30 SamzaContainer$ [INFO] Fetching configuration from:
> http://node03:54179/ <http://node03:54179/>*
> *2016-02-27 01:28:30 SamzaContainerExceptionHandler [ERROR] Uncaught
> exception in thread (name=main). Exiting process now.*
> *java.io.EOFException: No content to map to Object due to end of input*
> * at
> org.codehaus.jackson.map.ObjectMapper._initForReading(ObjectMapper.java:2775)*
> * at
> org.codehaus.jackson.map.ObjectMapper._readMapAndClose(ObjectMapper.java:2718)*
> * at
> org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:1863)*
> * at
> org.apache.samza.container.SamzaContainer$.readJobModel(SamzaContainer.scala:109)*
> * at
> org.apache.samza.container.SamzaContainer$.safeMain(SamzaContainer.scala:83)*
> * at
> org.apache.samza.container.SamzaContainer$.main(SamzaContainer.scala:66)*
> * at org.apache.samza.container.SamzaContainer.main(SamzaContainer.scala)*
> *End of LogType:samza-container-0.log*
>
>
>
> Can anyone help me figure out why it can't read the configuration file
> from the coordinator URL?
>
> Thanks,
>
>
> Jack Huang
>