You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@samza.apache.org by Anoop Krishnakumar <an...@gmail.com> on 2019/03/06 21:43:21 UTC
Trouble running samza 0.14 in standalone mode
I am prototyping an application where I have two input topics and two
output topics. The application also uses a rocksdb state store that is
backed by kafka.
I followed WikipediaZkLocalApplication example, but the application always
exits without listening for messages from topic. I could see the execution
plan and job coordinator communicating with zookeeper. I could see the
following line in logs
StreamProcessor [INFO] Container is not instantiated for stream processor:
5f7e2a46-fb7a-4054-bf5c-c62423ca2e35.
I could not figure out why the container wouldn't start. Any help would be
appreciated.
Attached is the log and the job configuration.
-anoop
Re: Trouble running samza 0.14 in standalone mode
Posted by Yi Pan <ni...@gmail.com>.
Great! Glad that you were able to figure it out!
-Yi
On Thu, Mar 7, 2019 at 3:14 AM Anoop Krishnakumar <
anoop.krishnakumar@gmail.com> wrote:
> Hi Yi,
>
> Apologies for my ignorance. I did not realize that attachments wont make
> through and gist is the preferred method of sharing logs and code snippets.
>
> Issue is resolved. I was using the default task.name.grouper.factory
> instead of GroupByContainerIdsFactory.
> Appreciate and thanks for the response. I will consider using 1.0 version.
>
> -anoop
>
>
> On Thu, 7 Mar 2019 at 01:41, Yi Pan <ni...@gmail.com> wrote:
>
> > Hi, Anoop,
> >
> > 1. Please provide the full log file if possible. Just listing out a
> single
> > log line reporting the failure does not help.
> > 2. Is there any reason that you still stay with Samza 0.14? I would
> highly
> > recommend to upgrade to 1.0 since there are tons of API and standalone
> > related improvements went in to that version after 0.14.
> >
> > -Yi
> >
> > On Wed, Mar 6, 2019 at 1:54 PM Anoop Krishnakumar <
> > anoop.krishnakumar@gmail.com> wrote:
> >
> > > I am prototyping an application where I have two input topics and two
> > > output topics. The application also uses a rocksdb state store that is
> > > backed by kafka.
> > >
> > > I followed WikipediaZkLocalApplication example, but the application
> > always
> > > exits without listening for messages from topic. I could see the
> > execution
> > > plan and job coordinator communicating with zookeeper. I could see the
> > > following line in logs
> > > StreamProcessor [INFO] Container is not instantiated for stream
> > processor:
> > > 5f7e2a46-fb7a-4054-bf5c-c62423ca2e35.
> > > I could not figure out why the container wouldn't start. Any help would
> > be
> > > appreciated.
> > >
> > > Attached is the log and the job configuration.
> > >
> > > -anoop
> > >
> >
>
Re: Trouble running samza 0.14 in standalone mode
Posted by Anoop Krishnakumar <an...@gmail.com>.
Hi Yi,
Apologies for my ignorance. I did not realize that attachments wont make
through and gist is the preferred method of sharing logs and code snippets.
Issue is resolved. I was using the default task.name.grouper.factory
instead of GroupByContainerIdsFactory.
Appreciate and thanks for the response. I will consider using 1.0 version.
-anoop
On Thu, 7 Mar 2019 at 01:41, Yi Pan <ni...@gmail.com> wrote:
> Hi, Anoop,
>
> 1. Please provide the full log file if possible. Just listing out a single
> log line reporting the failure does not help.
> 2. Is there any reason that you still stay with Samza 0.14? I would highly
> recommend to upgrade to 1.0 since there are tons of API and standalone
> related improvements went in to that version after 0.14.
>
> -Yi
>
> On Wed, Mar 6, 2019 at 1:54 PM Anoop Krishnakumar <
> anoop.krishnakumar@gmail.com> wrote:
>
> > I am prototyping an application where I have two input topics and two
> > output topics. The application also uses a rocksdb state store that is
> > backed by kafka.
> >
> > I followed WikipediaZkLocalApplication example, but the application
> always
> > exits without listening for messages from topic. I could see the
> execution
> > plan and job coordinator communicating with zookeeper. I could see the
> > following line in logs
> > StreamProcessor [INFO] Container is not instantiated for stream
> processor:
> > 5f7e2a46-fb7a-4054-bf5c-c62423ca2e35.
> > I could not figure out why the container wouldn't start. Any help would
> be
> > appreciated.
> >
> > Attached is the log and the job configuration.
> >
> > -anoop
> >
>
Re: Trouble running samza 0.14 in standalone mode
Posted by Yi Pan <ni...@gmail.com>.
Hi, Anoop,
1. Please provide the full log file if possible. Just listing out a single
log line reporting the failure does not help.
2. Is there any reason that you still stay with Samza 0.14? I would highly
recommend to upgrade to 1.0 since there are tons of API and standalone
related improvements went in to that version after 0.14.
-Yi
On Wed, Mar 6, 2019 at 1:54 PM Anoop Krishnakumar <
anoop.krishnakumar@gmail.com> wrote:
> I am prototyping an application where I have two input topics and two
> output topics. The application also uses a rocksdb state store that is
> backed by kafka.
>
> I followed WikipediaZkLocalApplication example, but the application always
> exits without listening for messages from topic. I could see the execution
> plan and job coordinator communicating with zookeeper. I could see the
> following line in logs
> StreamProcessor [INFO] Container is not instantiated for stream processor:
> 5f7e2a46-fb7a-4054-bf5c-c62423ca2e35.
> I could not figure out why the container wouldn't start. Any help would be
> appreciated.
>
> Attached is the log and the job configuration.
>
> -anoop
>
Re: Trouble running samza 0.14 in standalone mode
Posted by Bharath Kumarasubramanian <bk...@linkedin.com>.
Can you please attach the container logs? I noticed only job configurations were attached.
--
Bharath
From: Anoop Krishnakumar <an...@gmail.com>
Reply-To: "dev@samza.apache.org" <de...@samza.apache.org>
Date: Wednesday, March 6, 2019 at 1:54 PM
To: "dev@samza.apache.org" <de...@samza.apache.org>
Subject: Trouble running samza 0.14 in standalone mode
I am prototyping an application where I have two input topics and two output topics. The application also uses a rocksdb state store that is backed by kafka.
I followed WikipediaZkLocalApplication example, but the application always exits without listening for messages from topic. I could see the execution plan and job coordinator communicating with zookeeper. I could see the following line in logs
StreamProcessor [INFO] Container is not instantiated for stream processor: 5f7e2a46-fb7a-4054-bf5c-c62423ca2e35.
I could not figure out why the container wouldn't start. Any help would be appreciated.
Attached is the log and the job configuration.
-anoop